000014065 - Appliance 3.0 - ORA-31626: job does not exist

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014065
Applies ToAppliance 3.0.4
Issue

 


Successfully backup Primary or newly promoted replica that is now a primary


ORA-31626: job does not exist - ORA-39127: unexpected error from call to export_string
Backup fails - manage-backups fails
backup fails - manage-backups fails, from both Operations Console and command line rsautil manage-backups
ORA-39127: unexpected error from call to export_string := SYS.DBMS_RULE_EXP_RULES.create_exp(54274,'10.02.00.03.00',newblock) 

ORA-06502: PL/SQL: numeric or value error: character string buffer too small 

ORA-06512: ... 

Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCOBJ 

Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
 
CauseWhile the root cause has not yet been determined, the workaround presented here restores the ability to perform backups
Resolution

Open an SSH session to the primary and login as emcsrv


 


login: emcsrv
-bash-3.00$ sudo su rsaadmin


Password: ********


bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/utils


 


**The following command will pause replication and restart the database. During the database restart no authentication (user or administration) will occur on the primary. DO NOT SKIP THIS STEP **


 


bash-3.00$ ./rsautil manage-replication -a pause


Enter Master password: ***********


bash-3.00$ ./rsautil manage-secrets -a get com.rsa.db.root.password


Enter Master password: ***********


com.rsa.db.root.password: AAaaAAaaaa


bash-3.00$ .  ./rsaenv


bash-3.00$ sqlplus sys/AAaaAAaaaa as sysdba


 


SQL> @$ORACLE_HOME/rdbms/admin/catdph.sql


 


SQL> @$ORACLE_HOME/rdbms/admin/prvtdtde.plb


 


SQL> @$ORACLE_HOME/rdbms/admin/catdpb.sql


 


SQL> @$ORACLE_HOME/rdbms/admin/dbmspump.sql


 


SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql


 


SQL> exit


 


bash-3.00$ ./rsautil manage-replication -a resume


Enter Master password: ***********


 


 Backups should now succeed.


 

If the last command (utlrp.sql) fails or hangs OR if the ORA-31626 error persists, perform the steps below. Do not perform these steps if after running the above steps you can successfully take a backup.


bash-3.00$ cd usr/local/RSASecurity/RSAAuthenticationManager/utils 


 


stop database


 


./rsautil manage-database -a stop-db


 


start database


 


./rsautil manage-database -a start-db


 


pause replication


 


./rsautil manage-replication -a pause


 


sqlplus sys/AAaaAAaaaa as sysdba


SQL> select object_name, owner from dba_objects where status = 'INVALID';


 


Then:


 


SQL> BEGIN   SYS.UTL_RECOMP.RECOMP_PARALLEL(NULL, '<OWNER>'); end;


SQL> /


 


 


SQL> @ $ORACLE_HOME/rdbms/admin/utlrp.sql


 


./rsautil manage-replication -a resume


*********************************


EXAMPLE:


SQL> select object_name, owner from dba_objects where status = 'INVALID';


 


OBJECT_NAME


--------------------------------------------------------------------------------


 


OWNER


------------------------------


IMS_BATCH_REPLICATION_PKG


RSA_STREAMS_ADMIN


 


IMS_EVENT_MONITOR_JOB


SYS


 


*********************************


The above example shows two invalid objects. One is owned by RSA_STREAMS_ADMIN, the other is owned by SYS. You would need to issue the following commands to recompile each (if there is more than one job owned by the same user, they will all be recompiled):


SQL>BEGIN   SYS.UTL_RECOMP.RECOMP_PARALLEL(NULL, 'RSA_STREAMS_ADMIN'); end;


/


 


SQL>BEGIN   SYS.UTL_RECOMP.RECOMP_PARALLEL(NULL, 'SYS'); end;


/


  

Notes

 If you are experiencing this in Windows, see a50794

Legacy Article IDa50793

Attachments

    Outcomes