000028993 - Backup operation fails in the Operations Console in Appliance 3.0

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 Number000028993
Applies To
RSA Product SetSecurID
RSA Product/Service TypeRSA SecurID Appliance 3.0
RSA Version/Condition3.0 Service Pack 4
PlatformEMC CAP
Platform (Other)rPath Linux
O/S Version 
Product Name 
Product DescriptionRSA SecurID Appliance
IssueError message:
 
   com.rsa.ims.common.oracle.OracleException:   
   Please see log file at %1$s for more details.
   Exception:
   com.rsa.ims.common.oracle.OracleException: ORA-31626: job does not exist
    
   Error:
   com.rsa.common.SystemException: com.rsa.common.SystemException: com.rsa.ims.common.oracle.OracleException: ORA-31626: job does not exist
   Starting the RADIUS services
    

 
 
ResolutionResolve 1:
 
Try and stop and start the RSA Authentication Manager primary instance services at the command line as this is a less intrusive troubleshooting method. Where a service fails to start then report this to RSA Customer Support so we can collect the related log file to investigate further.
 
Stopping and starting RSA Authentication Manager 7.1 Service Pack 4 services on UNIX/SecurID Appliance
 
Steps:
1.Use emcsrv account to logon to the RSA SecurID Appliance 3.0
    
  
  • either at the local console or via an SSH session (SSH is enabled using the RSA Operations Console)
    
2.Use the command sudo su – rsaadmin to change the privileges
   The password for is the same as the emcsrv account
    
3.Navigate to the /usr/local/RSASecurity/RSAAuthenticationManager/server folder
    
4.Stop the RSA Authentication Manager 7.1 services
    
  
Stop./rsaam stop all
Start./rsaam start all

    
    

 
Example:
 
   bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/server
   bash-3.00$ ./rsaam stop all
   RSA Authentication Manager:                                [  OK  ]
   RSA Authentication Manager Administration Server:          [  OK  ]
   RSA Authentication Manager Node Manager:                   [  OK  ]
   RSA Authentication Manager Database Server:                [  OK  ]
   RSA Authentication Manager Database Listener:              [  OK  ]
   RSA Authentication Manager Operations Console:             [  OK  ]
   RSA Authentication Manager Radius:                         [  OK  ]
   RSA RADIUS Operations Console:                             [  OK  ]
   bash-3.00$

 
 
   bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/server
   bash-3.00$ ./rsaam start all
   RSA Authentication Manager Database Listener:              [  OK  ]
   RSA Authentication Manager Database Server:                [  OK  ]
   RSA Authentication Manager Node Manager:                   [  OK  ]
   RSA Authentication Manager Administration Server:          [  OK  ]
   RSA Authentication Manager:                                [  OK  ]
   RSA Authentication Manager Operations Console:/usr/bin/nohup: appending output to `nohup.out'
                                                              [  OK  ]
   RSA Authentication Manager Radius:                         [  OK  ]
   RSA RADIUS Operations Console:/usr/bin/nohup: appending output to `nohup.out'
                                                              [  OK  ]
   bash-3.00$

 
Resolve 2:
 
Checking the datapump (with instructions to reload the datapump)
 
These steps check the datapump integrity and provide a method to reload it should it be found corrupt.
 
Steps:
1.Use emcsrv account to logon to the RSA SecurID Appliance 3.0 (primary instance)
    
  
  • either at the local console or via an SSH session (SSH is enabled using the RSA Operations Console)
    
2.Use the command sudo su – rsaadmin to change the privileges
   The password for is the same as the emcsrv account
    
3.Navigate to the /usr/local/RSASecurity/RSAAuthenticationManager/utils folder
    
4.Acquire the password allowing for database access with the SQLplus program in a command prompt window.
    
   Open a Command Prompt and navigate to the <AMHOME>/utils folder and run the following commands as the user who has file ownership of the RSA Authentication Manager 7.1 software.
    
  
UNIX Usage./rsautil manage-secrets -a get com.rsa.db.root.password
      Enter Master password: ***********
      com.rsa.db.root.password: <password>

    
   Setup the environment using the rsaenv program found in the <AMHOME>/utils folder
    
  
UNIX Usage. ./rsaenv

    
    
5.Use the sqlplus program to run the script using the following instructions.
    
   Connect to the RSA Authentication Manager database with the sqlplus program from the <AMHOME>/utils folder using the command: sqlplus sys/<password> as sysdba
    
   NOTE: substitute <password> with the com.rsa.db.root.password found earlier.
    
   Example:
  
 
      sqlplus sys/<password> as sysdba
       
      SQL*Plus: Release 10.2.0.5.0 - Production on Wed Mar 27 10:17:54 2013
       
      Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.
       
       
      Connected to:
      Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production
      With the Partitioning, Data Mining and Real Application Testing options
       
      SQL>
       

    
    
6.Enter the following SQL statement (highlighted in bold):
    
   SQL> alter system set events '1403 trace name errorstack level 3';
    
    
7.In the Operations Console on the primary instance perform a backup and note any error messages, if any.
    
8.Back in the SQL*Plus program (at the command line) enter these SQL statements:
    
   SQL> alter system set events '1403 trace name errorstack off';
    
   SQL> select count(*) from DBA_OBJECTS where object_name = 'KUPC$DATAPUMP_QUETAB';
    
   SQL> analyze table kupc$datapump_quetab validate structure;
    
   Should the third SQL statement (analyze table command) generate an error then there is a corruption and the following SQL statements are needed to reload the datapump in the database:
    
   SQL> @/usr/local/RSASecurity/RSAAuthenticationManager/db/rdbms/admin/catdph.sql
    
   SQL> @/usr/local/RSASecurity/RSAAuthenticationManager/db/rdbms/admin/prvtdtde.plb
    
   SQL> @/usr/local/RSASecurity/RSAAuthenticationManager/db/rdbms/admin/catdpb.sql
    
   SQL> @/usr/local/RSASecurity/RSAAuthenticationManager/db/rdbms/admin/dbmspump.sql
    
   SQL> @/usr/local/RSASecurity/RSAAuthenticationManager/db/rdbms/admin/utlrp.sql
    
   SQL> exit
    
    

 
IMPORTANT NOTE: I ran through these steps for Resolve 2 on a working primary instance and was still able to perform a backup onto the local hard drive (/var/cap/backups) using the Operations Console > Maintenance > Backups > Backup Now option.
 
Example of Resolve 2:
 
   Here is an example where a problem was found:
    
   Using username "emcsrv".
   Last login: Tue Nov  4 10:38:47 2014 from aucsbellm1l1c.corp.emc.com
   -bash-3.00$ sudo su - rsaadmin
   Password:
   -bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
   -bash-3.00$ ./rsautil manage-secrets -a get com.rsa.db.root.password
   Enter Master password: ***********
   com.rsa.db.root.password: bgJmvo0zWd
   -bash-3.00$ . ./rsaenv
   -bash-3.00$ sqlplus sys/bgJmvo0zWd as sysdba
    
   SQL*Plus: Release 10.2.0.5.0 - Production on Tue Nov 4 10:43:58 2014
    
   Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.
    
    
   Connected to:
   Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production
   With the Partitioning, Data Mining and Real Application Testing options
    
   SQL> alter system set events '1403 trace name errorstack level 3';
    
   System altered.
    
   SQL> alter system set events '1403 trace name errorstack off';
    
   System altered.
    
   SQL> select count(*) from DBA_OBJECTS where object_name = 'KUPC$DATAPUMP_QUETAB';
    
     COUNT(*)
   ----------
            0
    
   SQL> analyze table kupc$datapump_quetab validate structure;
   analyze table kupc$datapump_quetab validate structure
                 *
   ERROR at line 1:
   ORA-00942: table or view does not exist
    
    
   SQL>
    
   NOTE: The following is expected from a working authentication manager instance:
    
   SQL> select count(*) from DBA_OBJECTS where object_name = 'KUPC$DATAPUMP_QUETAB';
    
     COUNT(*)
   ----------
            1
    
   SQL> analyze table kupc$datapump_quetab validate structure;
    
   Table analyzed.
    
   SQL>
    
    

 

Attachments

    Outcomes