Saturday, 15 October 2016

RMAN-05520

Versions 10.2, 11.1, 11.2, 12.1

Error:  RMAN-05520 database name mismatch, auxiliary instance has %s, command specified 
%s 
---------------------------------------------------------------------------
Cause:-
 The database name specified in the initialization parameter was not the same as the database name provided in the DUPLICATE command.


Solution:-

Correct the database name in the command or adjust the database name of the auxiliary instance.


OR

Rman leaves modified auxiliary spfile parameters if DUPLICATE fails (Doc ID 1283344.1) To BottomTo Bottom

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.1 [Release 11.2]
Information in this document applies to any platform.

SYMPTOMS:-

RMAN duplicate leaves behind an spfile for the auxiliary database if the duplicate fails with db_name set to the target db_name.
This causes subsequent rerun of the duplicate after fixing the failure to fail with:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/26/2010 13:22:29
RMAN-05520: database name mismatch, auxiliary instance has <target db_name>, command specified <auxilliary db_name>

CAUSE:-

Bug 9302045:  RMAN DUPLICATE W/O CONNECTION TO TARGET CREATES SPFILE WITH DB_NAME OF TARGET.

This is a duplicate of unpublished bug 9393650: IF AUXILIARY STARTED WITH SPFILE AND DUPLICATE FAILS SPFILE HAS BAD PARAMETERS

SOLUTION:-

Manually amend the auxiliary spfile prior to rerunning duplicate or request a backport of unpublished bug 9393650 to 11.2.0.1 for your platform.

Unpublished bug 9393650 is fixed in 11.2.0.2 Patch Set Release.

REFERENCES

BUG:9302045 - RMAN DUPLICATE W/O CONNECTION TO TARGET CREATES SPFILE WITH DB_NAME OF TARGET

Thursday, 6 October 2016

The XML Publisher Concurrent Request Fails Due to the Output Post Processing

Three possible errors can occur as below:
  • The Output Post Processor is not running or does not pick up the request

+————- 1) PUBLISH ————-+
Unable to find an Output Post Processor service to post-process request [request_id].
Check that the Output Post Processor service is running.
+————————————–+
Solutions:

* Verify that the Output Post Processor is enabled and active.
* If confirmed, retrieve the OPP log file either via the Forms application or via the Oracle Application Manager.
– Via the Forms application:
  1. Login to the application as SYSADMIN
  2. Responsibility: System Administrator
  3. Function: Concurrent –> Manager –> Administration
  4. Select the Output Post Processor
  5. Click on the Processes button
  6. Select the Concurrent Process which was active during the time that the request ran
  7. Click on the Manager Log button to open the Output Post Processor log file
– Via the Oracle Application Manager
  1. Login to the application as SYSADMIN
  2. Responsibility: System Administration
  3. Function: Oracle Applications Manager –> Concurrent Managers
  4. Select the Output Post Processor Service and click on View Details
  5. Click on View Processes
  6. Select the Concurrent Process which was active during the time that the request ran
  7. Click on the Log button to open the Output Post Processor log file
  • The Output Post Processor is running but has not picked up the request
...
+------------- 1) PUBLISH -------------+
The Output Post-processor is running but has not picked up
this request.No further attempts will be made to post-process
this request, and the request will be marked with Warning status.
Setting the profile option Concurrent: OPP Response Timeout
to a higher value may be necessary.
+--------------------------------------+
...
By default a timeout will occur if it takes longer then 120 seconds (2 min.) for the Output Post Processor to pick up the request from the Concurrent Manager process. In that case, the Concurrent Request will complete with status Warning and the Request log file will contain error message like above.
Solutions:

* Increase the value (in seconds) for the profile option ‘Concurrent:OPP Response Timeout‘.
  • The concurrent manager has timed out waiting for the Output Post-processor to finish this request

+————- 1) PUBLISH ————-+
The concurrent manager has timed out waiting for the Output Post-processor
to finish this request.
Check that there are enough Output Post-processor service processes running.
More information may be found in the service process logfile.
+————————————–+
The concurrent manager process has successfully invoked the OPP but it a timeout is encountered as the OPP takes too long to complete the job.
The time that this takes will depends on various elements such as:
  • size of the XML Data File
  • complexity of the template
  • performance of the server
  • ….
By default a timeout will occur if it takes longer then 300 seconds (5 min.) for the XML Publisher engine to generate the output file. The Concurrent Request will complete with status Warning and the Request log file will contain error message like above.
Solutions:
Increase the value (in seconds) for the profile option ‘Concurrent:OPP Process Timeout‘.

  • Output Post Processor (OPP) Log Contains Error “java.lang.OutOfMemoryError: Java heap space”

  • java.lang.reflect.InvocationTargetException Caused by:java.lang.OutOfMemoryError: Java heap space atoracle.xdo.parser.v2.XMLDocument.createNodeFromType(XMLDocument.java:2869) atoracle.xdo.parser.v2.XMLDocument.createNodeFromType(XMLDocument.java:3000)
Solutions:

1. Determine what the heap size per OPP process is currently:
  • select DEVELOPER_PARAMETERS from FND_CP_SERVICES
    where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
    where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);
2. The default should be:
  • J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m
3. Increase the Heap Space per Process to 1024:
  • update FND_CP_SERVICES
    set DEVELOPER_PARAMETERS = ‘J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m
    where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
    where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);
4. Bring the managers down.
5. Run cmclean.sql script from Note 134007.1 – CMCLEAN.SQL Non-Destructive Script to Clean Concurrent Manager Tables.
6. Bring the managers up again.
OR
1. Log into applications with the System Administrator responsibility.
2. Navigate to Concurrent -> Program -> Define
3. Query the XML Publisher Template Re-Generator program
4. Set the following value for the Executable Options : -Xmx1024m
5. Save changes.
6. Retest the program.
OR
Configure the XML Publisher Administrator Configuration settings.
1. As XML Publisher Administrator navigate to Administration->Configuration.
2. Under Temporary Directory pick a temporary file location on your concurrent processing node. This should be at least 5GB or 20x larger than largest XML data file you generate
3.  Under FO Processing, set:
o Use XML Publisher’s XSLT processor set to True
o Enable scalable feature of XSLT processor set to False
o Enable XSLT runtime optimization set to True

Not printing the output of this request because post-processing failed.

While seeing the request log got the following information

Post-processing of request 50834534 failed at 17-JUL-2012 16:43:23 with the error message:
The concurrent manager has timed out waiting for the Output Post-processor to finish this request.

Check that there are enough Output Post-processor service processes running.
More information may be found in the service process logfile.
+--------------------------------------+

+------------- 2) PRINT   -------------+
Not printing the output of this request because post-processing failed.
+--------------------------------------+

Solution:-
Increase the profile option “Concurrent:OPP Process Timeout”..

 Check User level profile setting if its blank the paricular user will use site level profile setting

OR

while checking the OPP manager log 
i picked the following  error 

Caused by: oracle.xdo.parser.v2.XPathException: Cannot convert 417,8955 to number

i think this is data issue....

Probably a data conversion error

Tuesday, 4 October 2016

ORA-28002

ORA-28002: the password will expire within 5 days.

Cause: The user's account is about to about to expire and the password needs 
to be changed.
Action: Change the password or contact the database administrator.

Solutions:

1) Simply change the password to avoid it temporary.
 [oracle@sujeet ~]$ sqlplus / as sysdba

SQL> conn system/password

ERROR:
ORA-28002: the password will expire within 5 days

Connected.

 [oracle@sujeet ~]$ sqlplus / as sysdba

SQL> alter user system identified by password;

User altered.

SQL> conn system/password

Connected.
2) Set PASSWORD_LIFE_TIME of the profile assigned user to UNLIMITED then 
change the password to avoid it permanently.

SQL> SELECT PROFILE FROM dba_users WHERE username = 'system';

PROFILE
--------------------------------------------------------------------------------
DEFAULT

SQL> SELECT  LIMIT FROM DBA_PROFILES WHERE PROFILE='DEFAULT' AND RESOURCE_NAME='PASSWORD_LIFE_TIME';

LIMIT
--------------------------------------------------------------------------------
180

 [oracle@sujeet ~]$ sqlplus / as sysdba

SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;

Profile altered.

SQL> SELECT ACCOUNT_STATUS FROM DBA_USERS WHERE USERNAME='system';

ACCOUNT_STATUS
--------------------------------
OPEN

SQL> conn system/password

Connected.

Issue Resolved.