No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionCloud 6.3.1.1 Troubleshooting Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Service Faults

Service Faults

Failed to Create a CDB

Symptom

The following message is displayed when DBCA is used to create a CDB database.

ORA-00200 control file could not be created
Possible Causes

The Oracle user does not have sufficient permissions on the specified directory. As a result, the control file cannot be created in the directory by using DBCA.

Procedure
  1. Use PuTTY to log in to the Oracle RAC cluster.

    Login address: management IP address of the Oracle RAC cluster
    NOTE:

    Contact the operation administrator to obtain the account and password for logging in to the Oracle RAC cluster.

  2. Check whether the Oracle user has the permission to create a control file in the directory.
  3. If the permission is insufficient, run the chown oracle:oinstall [Directory where the control file is located] command to change the permission on the directory.
  4. Use DBCA to create the CDB database again.

Failed to Start a CDB

Symptom

After a CDB is created, the CDB database cannot be started due to insufficient memory.

If the following information is displayed, the value of the Linux OS parameter kernel.shmall is too small.

ORA-27104: system-defined limits for shared memory was misconfigured
Possible Causes
  • If the value of the Linux OS parameter kernel.shmall is too small, the Oracle database cannot create sufficient shared memory. As a result, the startup fails.
  • If the OS memory is insufficient and the SGA size cannot be met, the Oracle database cannot be started.
Procedure
  1. Use PuTTY to log in to the Oracle host where a CDB fails to be created.

    Use the management IP address of the Oracle host where the CDB fails to be created for login.
    NOTE:

    Contact the operation administrator to obtain the account and password for logging in to the Oracle RAC cluster.

  2. Check whether the value of kernel.shmall in /etc/sysctl.conf is proper. The value of kernel.shmall indicates the maximum size of the shared memory segment that can be used by the system at a time. The unit is page. If the value of kernel.shmall is 2097152, the maximum size of the shared memory segment is 8 GB (2097152 x 4/1024/1024), and 4 indicates that the size of the memory page is 4 KB.
  3. The size of the SGA cannot exceed the value of this parameter. Otherwise, the CDB cannot be started. If the value of kernel.shmall does not meet the requirement, adjust the value of kernel.shmall and try to start the CDB again. If the kernel.shmall value is greater than the SGA size, go to 4.
  4. Run the free -g command to check whether the remaining memory of the system is greater than the size of the SGA.
  5. If the remaining memory is less than the parameter used for specifying the size of the CDB SGA, clear the system application to release the memory, or change the value of the parameter to a value smaller than the remaining memory.
  6. Restart the CDB.
  7. Contact technical support for assistance if the CDB still fails to be restarted.

Failed to Open a PDB After It Is Partially Restored

Symptom

After the database is restored to the state at a specified time or with a certain SCN, the following information is displayed when you open the database:

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
Possible Causes

After the Oracle PDB database is partially restored, you need to reset the sequence number of the redo logs.

Procedure
  1. Use PuTTY to log in to the Oracle RAC cluster.

    Login address: management IP address of the Oracle RAC cluster
    NOTE:

    Contact the operation administrator to obtain the account and password for logging in to the Oracle RAC cluster.

  2. Run the alter database open resetlogs command to open the database.
  3. Try to open the database again.
  4. Contact technical support for assistance if the database still fails to be opened.

Failed to Start an Oracle Listener

Symptom

The system displays a message indicating that the port is occupied when you run the srvctl start listener command to start the Oracle listener.

TNS-12542: TNS:address already in use
Possible Causes

The listener process or other application processes occupy the listening port. As a result, the Oracle listener cannot be started.

Procedure
  1. Use PuTTY to log in to the Oracle RAC cluster.

    Login address: management IP address of the Oracle RAC cluster
    NOTE:

    Contact the operation administrator to obtain the account and password for logging in to the Oracle RAC cluster.

  2. Run the netstat -ano | grep 1521 command to check whether the port is occupied. 1521 is the listening port of the listener.
  3. If the port is occupied but still needs to be used, run the kill command to kill the process occupying the port and restart the listener.
  4. If other listening ports can be used to start the listener, you can modify the listener configuration port to one unoccupied and restart the listener.

Failed to Recover a PDB

Symptom

"ORA-27037: unable to obtain file stat" alarm is reported when the PDB is recovered.

Possible Causes

Not all PDB nodes are stopped.

Procedure
  1. Use PuTTY to log in to the host of the PDB node.

    Login address: management IP address of the host of the PDB node
    NOTE:

    Contact the operation administrator to obtain the account and password for logging in to the Oracle RAC cluster.

  2. Run the su - oracle command to switch to user oracle.
  3. Run the ps -ef |grep smon command to check the status of the CDB to which the PDB belongs.

    oracle     6887     1   0 May23 ?         00:00:28 ora_smon_edcx1
    grid      12095     1   0 Apr12 ?         00:01:11 asm_smon_+ASM1
    root      12242     1   2 Apr12 ?         22:50:16 /home/u01/app/12.2.0/grid/product/db_1/bin/osysmond.bin
    oracle    33323 31607   0 10:57 pts/0     00:00:00 grep smon

  4. Run the export ORACLE_SID=edcx1 command and then sqlplus/as sysdba to connect to the CDB.
  5. Run the show pdbs command to check the status of all PDBs in the CDB.

    CON_ID CON_NAME                        OPEN MODE  RESTRICTED
    ------ ------------------------------- ---------- ----------
         2 PDB$SEED                        READ ONLY  NO
         3 DBBB                            READ WEITE NO
         4 DBEE                            READ WEITE NO
         5 FDSFS                           READ WEITE NO
         6 TTESTPDB                        READ WEITE NO
         7 DDDDD                           READ WEITE NO
         8 NYCTEST                         READ WEITE NO
         9 CQTEST01                        READ WEITE NO
        10 PDBSZL                          READ WEITE NO
        11 NYC111                          READ WEITE NO
        12 LALAL                           READ WEITE NO

  6. Find the PDB instance that fails to be restored, run the alter pluggable database DBBB close command to stop the PDB, and run the show pdbs command to check whether the PDB instance is successfully stopped.

    CON_ID CON_NAME                        OPEN MODE  RESTRICTED
    ------ ------------------------------- ---------- ----------
         2 PDB$SEED                        READ ONLY  NO
         3 DBBB                            MOUNTED
         4 DBEE                            READ WEITE NO
         5 FDSFS                           READ WEITE NO
         6 TTESTPDB                        READ WEITE NO
         7 DDDDD                           READ WEITE NO
         8 NYCTEST                         READ WEITE NO
         9 CQTEST01                        READ WEITE NO
        10 PDBSZL                          READ WEITE NO
        11 NYC111                          READ WEITE NO
        12 LALAL                           READ WEITE NO

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22725

Downloads: 37

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next