AIX

###########################################################################
Error:

$ ./sqlplus
exec(): 0509-036 Cannot load program sqlplus because of the following errors:
rtld: 0712-001 Symbol CreateIoCompletionPort was referenced
      from module /u01/app/oracle/product/12.1.0.2/db_1/lib/libttsh12.so(), but a runtime definition
      of the symbol was not found.
rtld: 0712-001 Symbol GetMultipleCompletionStatus was referenced
      from module /u01/app/oracle/product/12.1.0.2/db_1/lib/libttsh12.so(), but a runtime definition
      of the symbol was not found.
rtld: 0712-002 fatal error: exiting.
$

Solution:

Website:
https://blogs.sap.com/2015/04/10/error-in-oracle-12c-installation-rtld-0712-001-symbol-createiocompletionport-was-referenced/

 

 

Error in Oracle 12C installation – rtld: 0712-001 Symbol CreateIoCompletionPort was referenced



Installed Oracle 12C on AIX Server.
When executing “lsnrctl start”  or “lsnrctl status”    or sqlplus / as sysdba, error occurred
“rtld: 0712-001 Symbol CreateIoCompletionPort was referenced”.
12_1.JPG
12_2.JPG
The problem is due to I/O Communication ports either  not enabled  or not installed .
To check whether  IOCP is installed run the following command
# lslpp -l bos.iocp.rte
12_3.JPG
As shown above,  IOCP module was installed and present in AIX
To check whether IOCP is enabled or not , run the following unix command
# lsdev -Cc iocp

It showed “Defined” means not enabled. The output   should show “Available” instead of “Defined”.
To change from Defined to Available is done using  unix ‘smitty’ command
Log in as root and run the following command:
# smitty iocp
Select Change / Show Characteristics of I/O Completion Ports.
Change configured state at system restart from Defined to Available.
Run the lsdev command to confirm the IOCP status is set to Available:
# lsdev | grep iocp
     iocp0      Available       I/O Completion Ports
               

Perform a system  restart  (means server reboot) to make the changes permanent.
After the Server reboot, check lsnrctl status or lsnrctl start command  or sqlplus / as sysdba command as shown in the screenshot below

Before installing Oracle 12C, read the installation guide properly and follow the instructions  as  mentioned in the pre-requisite check.




###########################################################################

Error:
SQL> clear scr
SQL> Alter system set log_archive_dest_1='location= /archive/BISPNG' scope=both;
Alter system set log_archive_dest_1='location= /archive/BISPNG' scope=both
*
ERROR at line 1:
ORA-32017: failure in updating SPFILE
ORA-16179: incremental changes to "log_archive_dest_1" not allowed with SPFILE
SQL> clear scr
SQL> Alter system set log_archive_dest_1='location=/archive/BISPNG' scope=both;
System altered.

Solution: The error was caused due due to the space that exit between location= which get solved after removing the error.



Configuring IOCP on AIX

DB2 installation using the db2setup command or db2_install command enables IOCP and sets the status of the IOCP port to Available.
About this task
This topic describes how to configure I/O completion ports (IOCP) for AIX® 5.3 TL9 and AIX 6.1 TL2 . This version of AIX operating system has the IOCP fileset included as part of the base install.
Procedure
1.    Enter the lslpp command to check if the IOCP module is installed on your system:
$ lslpp -l bos.iocp.rte
Copy
The output from the lslpp command should be similar to the following :
Fileset                      Level  State      Description
         ----------------------------------------------------------------------------
        Path: /usr/lib/objrepos
         bos.iocp.rte               5.3.9.0  APPLIED    I/O Completion Ports API
 
        Path: /etc/objrepos
        bos.iocp.rte              5.3.0.50  COMMITTED  I/O Completion Ports API
Copy
2.    Enter the lsdev command to check if the status of the IOCP port is Available:
$ lsdev -Cc iocp
Copy
o    The output from the lsdev command should match the following example:
 iocp0 Available  I/O Completion Ports
Copy
o    If the IOCP port status is Defined, change the status to Available:
§  Log in to the server as root and issue the following command:
# smitty iocp
Copy
§  Select the Change / Show Characteristics of I/O Completion Ports. Change configured state at system restart from Defined to Available. Enter the lsdev command again and confirm that the status of the IOCP port is changed to Available.





3.9 Enabling I/O Completion Ports
To ensure successful database, client, and grid infrastructure installation, set IOCP to Available using this procedure.
On IBM AIX on POWER Systems (64-Bit), enable I/O completion ports (IOCP) to ensure successful database and grid infrastructure installation.
To check if the IOCP module is enabled, run the lsdev command:
$ lsdev | grep iocp
The following sample output shows the IOCP status is set to Defined and hence not enabled:
iocp0      Defined       I/O Completion Ports
By default, IOCP is set to Defined. To enable IOCP, set IOCP to Available using the following procedure:
  1. Log in as root and run the following command:
# smitty iocp
  1. Select Change / Show Characteristics of I/O Completion Ports.
  2. Change configured state at system restart from Defined to Available.
  3. Run the lsdev command to confirm the IOCP status is set to Available:
5.  $ lsdev | grep iocp
iocp0      Available       I/O Completion Ports
Restart the system to make the changes permanent.


###############################################################################




Automatic Shutdown and Startup of the Database:

2 Stopping and Starting Oracle Software

This chapter describes how to identify Oracle Database processes, and provides basic information about how to stop and restart them. It also describes how to set up automatic startup and shutdown of the Oracle Database. It contains the following sections:
Note:
When using Oracle Restart, you can use Service Control Utility (SRVCTL), a command-line interface, to manage Oracle processes (database instance, listener, Oracle ASM instance). With SRVCTL, you can manage the Oracle Restart configuration, see the status of processes managed by Oracle Restart, and start or stop processes such as Oracle Database. SRVCTL has been enhanced to support single instance databases with Oracle Restart on standalone servers and on clusters with Oracle Clusterware.
See Also:
Oracle Database Administrator's Guide and Oracle Automatic Storage Management Administrator's Guide for more information about SRVCTL commands

2.1 Stopping and Starting Oracle Processes

This section describes how to stop and start Oracle processes. It contains the following topics:

2.1.1 Stopping and Starting Oracle Database and Oracle Automatic Storage Management Instances

This section describes how to stop and start Oracle Database and Oracle Automatic Storage Management instances.

2.1.1.1 Stopping an Oracle Database or Oracle Automatic Storage Management Instance

Caution:
Do not stop an Oracle Automatic Storage Management instance until you have stopped all Oracle Database instances that use Oracle Automatic Storage Management instance to manage their storage.
To stop an Oracle Database or Oracle Automatic Storage Management instance:
1.       Run the following commands to identify the SID and Oracle home directory for the instance that must be shut down:
On Oracle Solaris:
$ cat /var/opt/oracle/oratab
On other operating systems:
$ cat /etc/oratab
The oratab file contains lines similar to the following, which identify the SID and corresponding Oracle home directory for each database or Oracle Automatic Storage Management instance on the system:
$ORACLE_SID:$ORACLE_HOME:<N|Y>
Note:
Oracle recommends that you use the plus sign (+) as the first character in the SID of Oracle Automatic Storage Management instances.
2.       Run the oraenv or coraenv script, depending on the default shell, to set the environment variables for the instance that must be shut down:
o    Bourne, Bash, or Korn shell:
o    $ . /usr/local/bin/oraenv
o    C shell:
o    % source /usr/local/bin/coraenv
When prompted, specify the SID for the instance.
3.       Run the following commands to shut down the instance:
4.  $ sqlplus
5.  SQL> CONNECT SYS as SYSDBA
6.  Enter password: sys_password
7.  SQL> SHUTDOWN NORMAL
After the instance shuts down, you can quit SQL*Plus.

2.1.1.2 Restarting an Oracle Database or Oracle Automatic Storage Management Instance

Caution:
If the database instance uses Oracle Automatic Storage Management for storage management, then you must start the Oracle Automatic Storage Management instance before you start the database instance.
To restart an Oracle Database or Oracle Automatic Storage Management instance:
1.       Repeat steps 1 and 2, if required, to set the ORACLE_SID and ORACLE_HOME environment variables to identify the SID and Oracle home directory for the instance you want to start.
2.       Run the following commands to start the instance:
3.  $ sqlplus
4.  SQL> CONNECT SYS as SYSDBA
5.  Enter password: sys_password
6.  SQL> STARTUP
After the instance starts, you can exit from SQL*Plus.

2.1.2 Stopping and Starting Oracle Restart

To stop or start Oracle Restart, run the following command:
·         Start: This option is used to start Oracle Restart
Syntax and Options:
crsctl start has
·         Stop: This option is used to stop Oracle Restart
Syntax and Options:
crsctl stop has
See Also:
Oracle Database Administrator's Guide for more information about the srvctl commands

2.2 Automating Shutdown and Startup

Oracle recommends that you configure the system to automatically start Oracle Database when the system starts, and to automatically shut it down when the system shuts down. Automating database startup and shutdown guards against incorrect database shutdown.
To automate database startup and shutdown, use the dbstart and dbshut scripts, which are located in the $ORACLE_HOME/bin directory. The scripts refer to the same entries in the oratab file, which are applied on the same set of databases. You cannot, for example, have the dbstart script automatically start sid1, sid2, and sid3, and have the dbshut script shut down only sid1. However, you can specify that the dbshut script shuts down a set of databases while the dbstart script is not used at all. To do this, include a dbshut entry in the system shutdown file, but do not include the dbstart entry from the system startup files.
See Also:
The init command in the operating system documentation for more information about system startup and shutdown procedures

2.2.1 Automating Database Startup and Shutdown on Other Operating Systems

To automate database startup and shutdown by using the dbstart and dbshut scripts:
1.       Log in as the root user.
2.       Edit the oratab file for the platform.
To open the file, use one of the following commands:
o    On Oracle Solaris:
o    # vi /var/opt/oracle/oratab
o    On IBM AIX on POWER Systems (64-Bit) and Linux:
o    # vi /etc/oratab
Database entries in the oratab file are displayed in the following format:
$ORACLE_SID:$ORACLE_HOME:<N|Y>
In this example, the values Y and N specify whether you want the scripts to start or shut down the database, respectively. For each database for which you want to automate shutdown and startup, first determine the instance identifier (SID) for that database, which is identified by the SID in the first field. Then, change the last field for each to Y.
You can set dbstart to autostart a single-instance database which uses an Automatic Storage Management installation auto-started by Oracle Clusterware. This is the default behavior for an Automatic Storage Management cluster. To do this, you must change the oratab entry of the database and the Automatic Storage Management installation to use a third field with the value Wand N, respectively. These values specify that dbstart auto-starts the database only after the Automatic Storage Management instance is started.
Note:
If you add new database instances to the system and automate the startup for them, then you must edit the entries for those instances in the oratab file.
3.       Change directory to one of the following, depending on the operating system:
Platform
Initialization File Directory
Linux and Oracle Solaris
/etc/init.d
IBM AIX on POWER Systems (64-Bit)
/etc
  1.  
5.       Create a file called dbora, and copy the following lines into this file:
Note:
Change the value of the ORACLE_HOME environment variable to specify the Oracle home directory for the installation. Change the value of the ORACLE environment variable to the user name of the owner of the database installed in the Oracle home directory (typically, oracle).
#! /bin/sh 
# description: Oracle auto start-stop script.
#
# Set ORACLE_HOME to be equivalent to the $ORACLE_HOME
# from which you wish to execute dbstart and dbshut;
#
# Set ORA_OWNER to the user id of the owner of the
# Oracle database in ORACLE_HOME.
 
ORA_HOME=<Type your ORACLE_HOME in full path here>
ORA_OWNER=<Type your Oracle account name here>
 
case "$1" in
'start')
    # Start the Oracle databases:
    # The following command assumes that the oracle login
    # will not prompt the user for any values
    # Remove "&" if you don't want startup as a background process.
    su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME" &
    touch /var/lock/subsys/dbora
    ;;
 
'stop')
    # Stop the Oracle databases:
    # The following command assumes that the oracle login
    # will not prompt the user for any values
    su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME" &
    rm -f /var/lock/subsys/dbora
    ;;
esac




other Examples: 


====================================================================




#! /bin/sh 
# description: Oracle auto start-stop script.
#
# Set ORACLE_HOME to be equivalent to the $ORACLE_HOME
# from which you wish to execute dbstart and dbshut;
#
# Set ORA_OWNER to the user id of the owner of the
# Oracle database in ORACLE_HOME.
 
ORA_HOME=/u01/app/oracle/product/12.2.0.1/db_1
ORA_OWNER=oracle
 
case "$1" in
'start')
    # Start the Oracle databases:
    # The following command assumes that the oracle login
    # will not prompt the user for any values
    # Remove "&" if you don't want startup as a background process.
    su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME" 
    su - $ORA_OWNER -c "/u01/app/oracle/config/domains/ncdc_domain/bin/startWebLogic.sh" 
    touch /var/lock/subsys/dbora
    ;;
 
'stop')
    # Stop the Oracle databases:
    # The following command assumes that the oracle login
    # will not prompt the user for any values
    su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME" &
    rm -f /var/lock/subsys/dbora
    ;;
esac





====================================================================













Note:



This script can only stop Oracle Net listener for which a
password has not been set. In addition, if the listener name is not the default
name, LISTENER, then you must specify the listener name in the stop and start commands:




$ORACLE_HOME/bin/lsnrctl {start|stop} listener_name





6.      
Change the group of the dbora file to the OSDBA group (typically dba), and set the permissions to 750:




7.  # chgrp dba dbora


8.  # chmod 750 dbora





9.      
Create symbolic links to the dbora script in the appropriate run-level script
directories, as follows:





 


   

Platform


   

Symbolic Links Commands


  


 


  

Oracle Solaris


  


# ln -s /etc/init.d/dbora /etc/rc0.d/K01dbora


# ln -s /etc/init.d/dbora /etc/rc3.d/S99dbora




 



  

Linux


  


# ln -s /etc/init.d/dbora /etc/rc.d/rc0.d/K01dbora


# ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S99dbora


# ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S99dbora




 



  

IBM AIX on POWER Systems (64-Bit)


  


# ln -s /etc/dbora /etc/rc.d/rc2.d/S99dbora


# ln -s /etc/dbora /etc/rc.d/rc0.d/K01dbora




 















###############################################################################























































No comments:















Post a Comment























        

      









Subscribe to:
Posts (Atom)