How to Stop Oracle Audit Vault Services

Simple article on stopping Oracle Audit Vault Services.

Follow below  sequence of steps:

/usr/local/dbfw/bin/javafwk stop --> From root
/usr/local/dbfw/bin/dbfwdb stop --> From oracle
/usr/local/dbfw/bin/asmdb stop --> From root

[root@auditvault02 ~]# /usr/local/dbfw/bin/javafwk stop
Stopping Java framework...                                 [  OK  ]
[root@auditvault02 ~]#

[root@auditvault02 ~]# su - oracle
[oracle@auditvault02 ~]$
[oracle@auditvault02 ~]$ /usr/local/dbfw/bin/dbfwdb stop
Shutting down the database
Database shut down
[oracle@auditvault02 ~]$
[oracle@auditvault02 ~]$ lsnrctl stop

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 27-SEP-2018 10:51:53

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
The command completed successfully
[oracle@auditvault02 ~]$
[oracle@auditvault02 ~]$

[root@auditvault02 ~]#
[root@auditvault02 ~]# /usr/local/dbfw/bin/asmdb stop
[root@auditvault02 ~]#

[root@auditvault02 ~]#
[root@auditvault02 ~]# su - grid
[grid@auditvault02 ~]$ lsnrctl stop LISTENER_ASM

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 27-SEP-2018 10:51:34

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1523)))
The command completed successfully
[grid@auditvault02 ~]$


Now follow the reverse to restart up avdf DB and APP services.

Output file was found but is zero sized - Deleted

Output file was found but is zero sized - Deleted

I go a call from our developer that request are completing in warning status.

On investigation i found blow errors in OPP logs.

Error

[092618_131735369][][EXCEPTION] [DEBUG]  [sun.cpu.isalist]:[]
[9/26/18 1:17:35 PM] [1648558:RT19832034] Output file was found but is zero sized - Deleted
[9/26/18 1:17:35 PM] [UNEXPECTED] [1648558:RT19832034] java.io.FileNotFoundException: /d01/Prod/temp_xml/xdo6QGDTbJCca092618_1317356982.fo (Permission denied)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:145)
        at oracle.apps.xdo.common.tmp.TmpFile.createTmpFileJDK118(TmpFile.java:146)
        at oracle.apps.xdo.common.tmp.TmpFile.createTmpFile(TmpFile.java:113)
        at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:987)
        at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
        at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1647)
        at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:941)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5936)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
        at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:302)
        at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)

[9/26/18 1:17:35 PM] [1648558:RT19832034] Completed post-processing actions for request 19832034.


Cause 

The Temporary directory for XML Publisher has not been modified after making the clone so it was pointing to non existing location and getting error out.

Solution

1. Create a new Temporary Directory on OS level for the cloned environment.
2. Make sure that the application owner (APPLMGR) has Read and Write permission this directory.
3. Setup this new directory for XML Publisher via : XML Publisher Administrator responsibility: Properties -> General -> Temporary Directory.
3. Restart the Server.
4. Test again with a XML Publisher Report.

Disable BI Publisher Enterprise Manager 13c

Enterprise Manager 13c – Disable the BI Publisher

The BI Publisher will be started automatically during the startup process of the Enterprise Manager 13c. You don’t like the BI Publisher or you don’t use it? Save the resources, speed up your startup process, disable it. The password of the database repository owner SYSMAN is required.

Verify the Status – the BI Publisher is up and running

[oracle@vivaoem bin]$ ./emctl status oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
BI Publisher Server is Up
[oracle@vivaoem bin]$

Yes it was up, lets disable it.

[oracle@vivaoem bin]$ ./emctl config oms -disable_bip
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Stopping BI Publisher Server...
BI Publisher Server Successfully Stopped
BI Publisher Server is Down
BI Publisher has been disabled on this host and will not be started with the 'emctl start oms' or 'emctl start oms -bip_only' commands.
Overall result of operations: SUCCESS
[oracle@vivaoem bin]$
[oracle@vivaoem bin]$ ./emctl status oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
BI Publisher Server is Down
BI Publisher is disabled, to enable BI Publisher on this host, use the 'emctl config oms -enable_bip' command
[oracle@vivaoem bin]$

Please note its just an temporary disable, on future restart of EM services BIP will be started again, you need to disable it again.

RMAN-06026: some targets not found - aborting restore

I was cloning one of our TEST and server and stuckup on "RMAN-06026 and RMAN-06023" while restoring database.

RMAN> run
{
SET NEWNAME FOR DATABASE   TO  '/u01/oracle/app/gbldrsdata/%b';
SET NEWNAME FOR tempfile  1 TO '/u01/oracle/app/gbldrsdata/%b';
restore database ;
switch datafile all;
switch tempfile all;
set until sequence 20686 thread 1;
recover database;
}2> 3> 4> 5> 6> 7> 8> 9> 10>

executing command: SET NEWNAME
executing command: SET NEWNAME

Starting restore at 10-AUG-18
using channel ORA_DISK_1
using channel ORA_DISK_2

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/10/2018 00:52:27
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore

RMAN>

After drill-down i found that there are some backup files in FRA that belongs to OLD INCARNATION, as i was not interested in these files i have disabled FRA.

commented *.db_recovery_file_dest and *.db_recovery_file_dest_size in pfile and restarted restore and it went successful.

Function not available to this responsibility When Trying to Access Custom Form

When attempting to access custom forms, the following error occurs.

"Function not available to this responsibility. Change Responsibilities or contact your System Administrator".

Cause: Missing entry of CUSTOM_TOP under default.env file.

Solution:

Below procedure requrired to function cutom entry

1. Add  missing CUSTOM_TOP entry to $INST_TOP/ora/10.1.2/forms/server/default.env
XX_TOP=/d01/Prod/apps/apps_st/appl/xx_top/12.0.0

2. Add XX_TOP entry to CONTEXT_FILE

<XX_TOP oa_var="s_xxtop" oa_type="PROD_TOP" oa_enabled="FALSE">/d01/Prod/apps/apps_st/appl/xx_top/12.0.0</XX_TOP>

3. source APPSPROD_XXX.env

4. Restart Middle Tier services.