5 Reset Passwords for Oracle and BI Publisher Database Users

The Oracle database (OCSREMDW) user password and the BI Publisher database user passwords (DEV_MDS, DEV_BIPLATFORM, NNCENTRAL) that you configured in the Report Manager installation expires after 180 days. Use the tasks in this chapter to reset any of these passwords before they expire.

Seven days before the Oracle database or BI Publisher passwords expire, an alarm displays in the Fault Manager, Alarms pane that indicates that any one of these passwords need to be reset. These alarms are prompted by the apNNCReportingPswdExpiration trap. The apNNCReportingPswdExpirationClear trap clears the warning in the pane once these passwords are reset. If you are using Report Manager in an SDM cluster, each cluster member node sends out a warning event before a password expires. However, when this warning event is cleared, the clearing event only indicates the server from which the clear trap was generated (even though the other cluster member nodes may also be in a clear state).

Note:

If you need to modify when to receive the notification, you can edit the BEServerConfig.xml file using the "daysBeforeExpirationToCheck" option. The file is located in the following SDM server directory: 
/AcmePacket/NNC<version>/conf/BEServerConfig.xml

Reset the Password for the Oracle Database User

  1. Login to the server on which SDM is installed with the nncentral user. 
    ssh -Y nncentral@<OCSDM-Linux-server>
  2. Change directory to the SDM bin directory. 
    cd /home/nncentral/AcmePacket/NNC<version>/bin
  3. Execute the shutdownnnc.sh script. By default, the shutdownnnc.sh script detects whether the existing installation is a standalone or clustered system and prompts you with the option to shut down the entire cluster if no flag options are provided.

    Note:

    You can script an option ahead of time by adding -local for single nodes and -cluster to shutdown an entire cluster. 
    ./shutdownnnc.sh
Shutdown back-end server
Do you wish to shut down the entire cluster (Yes/No)? Yes
  4. Go to the Oracle database bin home directory. 
    cd $ORACLE_HOME/bin
  5. Specify the Oracle SID to ocsdmdw. 
    export ORACLE_SID=ocsdmdw
  6. Connect to the Oracle database as the Oracle system administrator (sysdba). 
    ./sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 29 10:29:14 2017

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production

SQL>
  7. Check the OCSREMDW user status. 
    SQL> select username, account_status from dba_users where username = 'OCSREMDW';

USERNAME                       ACCOUNT_STATUS
------------------------------ --------------------------------
OCSREMDW                       LOCKED
  8. If the status is in the LOCKED status (the status before the password expires) then you must unlock the OCSREMDW user account before you reset the password. If there is a different status, such as OPEN, EXPIRED and LOCKED, or EXPIRED, skip this step and proceed to step 9. 
    SQL> alter user ocsremdw account unlock;

User altered.
  9. Reset the OCSREMDW password by entering the original password that was specified during original database installation. 
    SQL> alter user ocsremdw identified by <original password>;

User altered.
  10. Logout as the Oracle system administrator (sysdba). 
    SQL> exit;
Disconnected from Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
  11. Connect to OCSDMDW database as the OCSREMDW user to ensure that the database is operational. 
    ./sqlplus ocsremdw/<password>@ocsdmdw

SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 29 10:43:17 2017

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production

SQL>
  12. Logout as the OCSREMDW user. 
    SQL> exit;
Disconnected from Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
  13. Change to the SDM server bin directory. 
    cd /home/nncentral/AcmePacket/NNC<version>/bin
  14. Start the SDM server. 
    ./startnnc.sh
  15. Check the Reporting Service log to make sure that it was started successfully. 
    cd <OCSDM-INSTALL_DIRECTORY>/logs
grep "service started" ReportingService.log
2016-02-09 16:44:37,988 INFO [com.acmepacket.ems.server.services.ReportingService] - Method: [startService]
Thread: [ReportingService:25]  Msg:[...service started]
  16. If you are running an SDM server cluster, repeat the previous steps for each cluster member node.

Reset the Password for BI Publisher Users

  1. Login to the server on which the BI Publisher application is installed. 
    ssh -Y oracle@<BI-Publisher-server>
  2. Change directory to the SDM bin directory (if the BI Publisher application is running on the same server as SDM). 
    cd /home/nncentral/AcmePacket/NNC<version>/bin
  3. Execute the shutdownnnc.sh script (if the BI Publisher application is running on the same server as SDM). By default, the shutdownnnc.sh script detects whether the existing installation is a standalone or clustered system and prompts you with the option to shut down the entire cluster if no flag options are provided.

    Note:

    You can script an option ahead of time by adding -local for single nodes and -cluster to shutdown an entire cluster. 
    ./shutdownnnc.sh
Shutdown back-end server
Do you wish to shut down the entire cluster (Yes/No)? Yes
  4. Stop the WebLogic server by running the stopWeblogic.sh script. 
    cd /app/OracleMiddleWare/user_projects/domains/bifoundation_domain/bin/
./stopWebLogic.sh
    The default user name is weblogic.
  5. Go to the Oracle database bin home directory. 
    cd $ORACLE_HOME/bin
  6. Specify the Oracle session identifier (SID).
    For example: 
    export ORACLE_SID=AcmeBIPublis
  7. Connect to the Oracle database as the Oracle system administrator (sysdba). 
    ./sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 29 10:29:14 2017

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production

SQL>
  8. Check the user account status for the BI Publisher database user passwords (DEV_MDS, DEV_BIPLATFORM, or NNCENTRAL).
    For example: 
    SQL> select username, account_status from dba_users where username = 'DEV_MDS';

USERNAME                       ACCOUNT_STATUS
------------------------------ --------------------------------
DEV_MDS                       LOCKED
  9. If the status is in the LOCKED status (the status before the password expires) then you must unlock the BI Publisher database user account before you reset the password. If there is a different status, such as OPEN, EXPIRED and LOCKED, or EXPIRED, skip this step and proceed to step 10.
    For example: 
    SQL> alter user DEV_MDS account unlock;

User altered.
  10. Reset the BI Publisher database user passwords (DEV_MDS, DEV_BIPLATFORM, or NNCENTRAL) by entering their original passwords that were specified during original database installation. 
    SQL> alter user DEV_MDS identified by <original password>;

User altered.
  11. Logout as the Oracle system administrator (sysdba). 
    SQL> exit;
Disconnected from Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
  12. Connect to BI Publisher database as one of the BI Publisher database users (DEV_MDS, DEV_BIPLATFORM, or NNCENTRAL) to ensure that the database is operational.
    For example: 
    ./sqlplus DEV_MDS/<password>@AcmeBIPublis

SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 29 10:43:17 2017

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production

SQL>
  13. Logout as any one of the BI Publisher database users (DEV_MDS, DEV_BIPLATFORM, or NNCENTRAL). 
    SQL> exit;
Disconnected from Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
  14. Login again as the Oracle user and start BI Publisher on the WebLogic server.

    Note:

    If you have any problems starting BI Publisher, see the Restart the WebLogic Server to Run Reports section in the Oracle Communications Report Manager Installation Guide for more information. 
    nohup ./startWeblogic.sh &
  15. Check the Weblogic server log to make sure that it was started successfully.
  16. Switch to the nncentral user. 
    su nncentral
  17. Change to the SDM server bin directory. 
    cd /home/nncentral/AcmePacket/NNC<version>/bin
  18. Start the SDM server. 
    ./startnnc.sh
  19. Check the Reporting Service log to make sure that it was started successfully. 
    cd <OCSDM-INSTALL_DIRECTORY>/logs
grep "service started" ReportingService.log
2016-02-09 16:44:37,988 INFO [com.acmepacket.ems.server.services.ReportingService] - Method: [startService]
Thread: [ReportingService:25]  Msg:[...service started]
  20. If you are running an SDM server cluster, repeat the previous steps for each cluster member node.