Today I change the IP address of my development server (linux redhat 5) with
Root# ifconfig eth0 10.11.201.250 netmask 255.255.255.0 up
Root# ifconfig eth0
And
I change this IP in my /etct/hosts file.
After this when I am trying to start my listener, its says following error…..
[oracle@ebek ~]$ lsnrctl start
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Starting /opt/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.4.0 - Production
System parameter file is /opt/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /opt/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ebek)(PORT=1521)))
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.11.201.250)(PORT=1521)))
TNS-12542: TNS:address already in use
TNS-12560: TNS:protocol adapter error
TNS-00512: Address already in use
Linux Error: 98: Address already in use
Listener failed to start. See the error message(s) above...
================================================================
Solution:-
================================================================
After that I also change my target Ip and subnet mask in the following files.
And reboot the server. My problem is solved.
Root# vi /etc/sysconfig/network-scripts/ifcfg-eth0
And
Root# vi /etc/sysconfig/network
Halim, a Georgia Tech graduate Senior Database Engineer/Data Architect based in Atlanta, USA, is an Oracle OCP DBA and Developer, Certified Cloud Architect Professional, and OCI Autonomous Database Specialist. With extensive expertise in database design, configuration, tuning, capacity planning, RAC, DG, scripting, Python, APEX, and PL/SQL, he combines technical mastery with a passion for innovation. Notably, Halim secured 16th place worldwide in PL/SQL Challenge Cup Playoff on the year 2010.
Tuesday, March 20, 2012
Monday, March 19, 2012
Auto startup and shutdown oracle database in linux
Auto startup and shutdown oracle database in linux or sun solaris
=================================================================
Down this file
https://www.dropbox.com/s/yrrpy0eta8qmdt3/auto_startup%20database%20in%20linux.txt
1) change a flag ( from N to Y) for auto starup the instance (there may be more than one instance, you should change every instance flag)
In Linux
===========
[ oratab file will create when you run (two script at installation of oracle finishing time) with root user ]
root# vi /etc/oratab
orcl:/d02/oracle/ora102:Y
In sun solaris
===================
root# vi /var/opt/oracle/oratab
orcl:/d02/oracle/ora102:Y
2)
First create(with oracle user) two "start_db" and "stop_db" script
in your $ORACLE_HOME/bin that starts and stop the db.
scripts are below... be careful about copy/paste.try to write it
with your own hand in linux.
-------------------start_db script
#!/bin/bash
# Start the Oracle Database and listeners
su - oracle<
lsnrctl start
sqlplus /nolog<
connect / as sysdba
startup
EOS
#emctl start dbconsole
#isqlplusctl start
EOO
---------------stop_db script
#!/bin/bash
# Stop the Oracle Database and linteners
su - oracle<
lsnrctl stop
sqlplus /nolog<
connect / as sysdba
shutdown immediate
EOS
#emctl stop dbconsole
#isqlplusctl stop
EOO
3) (with root user)
add to the /etc/rc3.d/S99local script something like:
#!/bin/sh
# chkconfig: 345 99 10
case "$1" in
'start') su - oracle -c start_db ;;
'stop') su - oracle -c stop_db ;;
esac
or
you can make a script like /etc/init.d/db_start_stop
and give the following permission and association.
chmod 750 /etc/init.d/db_start_stop
chkconfig --add db_start_stop
4) for test your script with root user
-----------------------------
#!/bin/sh
# chkconfig: 345 99 10
case "$1" in
'start') su - oracle -c start_db ;;
'stop') su - oracle -c stop_db ;;
esac
--------------------------------
(note: make a script with above code name in
"/etc/init.d/db_start_stop"
#sh /etc/init.d/db_start_stop start
#sh /etc/init.d/db_start_stop stop
----------------extra---for--me--only----------------------
============================================================================
i was facing "standard in must be a tty" this message when testing to run
these commands
#sh /etc/init.d/db_start_stop start
#sh /etc/init.d/db_start_stop stop
solution:-
I am making change in this script
#!/bin/sh
# chkconfig: 345 99 10
case "$1" in
'start') su - oracle -c start_db ;;---change----su - root -c /oracle_home_details/bin/start_db ;;
'stop') su - oracle -c stop_db ;; ---change----su - root -c /oracle_home_details/bin/stop_db ;;
esac
==========================================================
note : for Associating the db_start_stop service with the appropriate run levels and set it to auto-start using the following command.
chmod 750 /etc/init.d/db_start_stop
chkconfig --add db_start_stop
=================================================================
Down this file
https://www.dropbox.com/s/yrrpy0eta8qmdt3/auto_startup%20database%20in%20linux.txt
1) change a flag ( from N to Y) for auto starup the instance (there may be more than one instance, you should change every instance flag)
In Linux
===========
[ oratab file will create when you run (two script at installation of oracle finishing time) with root user ]
root# vi /etc/oratab
orcl:/d02/oracle/ora102:Y
In sun solaris
===================
root# vi /var/opt/oracle/oratab
orcl:/d02/oracle/ora102:Y
2)
First create(with oracle user) two "start_db" and "stop_db" script
in your $ORACLE_HOME/bin that starts and stop the db.
scripts are below... be careful about copy/paste.try to write it
with your own hand in linux.
-------------------start_db script
#!/bin/bash
# Start the Oracle Database and listeners
su - oracle<
sqlplus /nolog<
startup
EOS
#emctl start dbconsole
#isqlplusctl start
EOO
---------------stop_db script
#!/bin/bash
# Stop the Oracle Database and linteners
su - oracle<
sqlplus /nolog<
shutdown immediate
EOS
#emctl stop dbconsole
#isqlplusctl stop
EOO
3) (with root user)
add to the /etc/rc3.d/S99local script something like:
#!/bin/sh
# chkconfig: 345 99 10
case "$1" in
'start') su - oracle -c start_db ;;
'stop') su - oracle -c stop_db ;;
esac
or
you can make a script like /etc/init.d/db_start_stop
and give the following permission and association.
chmod 750 /etc/init.d/db_start_stop
chkconfig --add db_start_stop
4) for test your script with root user
-----------------------------
#!/bin/sh
# chkconfig: 345 99 10
case "$1" in
'start') su - oracle -c start_db ;;
'stop') su - oracle -c stop_db ;;
esac
--------------------------------
(note: make a script with above code name in
"/etc/init.d/db_start_stop"
#sh /etc/init.d/db_start_stop start
#sh /etc/init.d/db_start_stop stop
----------------extra---for--me--only----------------------
============================================================================
i was facing "standard in must be a tty" this message when testing to run
these commands
#sh /etc/init.d/db_start_stop start
#sh /etc/init.d/db_start_stop stop
solution:-
I am making change in this script
#!/bin/sh
# chkconfig: 345 99 10
case "$1" in
'start') su - oracle -c start_db ;;---change----su - root -c /oracle_home_details/bin/start_db ;;
'stop') su - oracle -c stop_db ;; ---change----su - root -c /oracle_home_details/bin/stop_db ;;
esac
==========================================================
note : for Associating the db_start_stop service with the appropriate run levels and set it to auto-start using the following command.
chmod 750 /etc/init.d/db_start_stop
chkconfig --add db_start_stop
Sunday, February 26, 2012
Heap size K exceeds notification threshold (2048K)
Memory Notification: Library Cache Object loaded into SGA
Heap size 2294K exceeds notification threshold (2048K)
-------------------------------------------------------------
These are warning messages that should not cause the program responsible for these errors to fail. They appear as a result of new event messaging mechanism and memory manager in 10g Release 2.
The meaning is that the process is just spending a lot of time in finding free memory extents during an allocate as the memory may be heavily fragmented. Fragmentation in memory is impossible to eliminate completely, however, continued messages of large allocations in memory indicate there are tuning opportunities on the application.
[ Note:- Set _kgl_large_heap_warning_threshold to a reasonable high value or zero to prevent these warning messages. Value needs to be set in bytes.
The default threshold in 10.2.0.1 is 2MB. So these messages could show up frequently in some application environments.
In 10.2.0.2, the threshold was increased to 50MB after regression tests, so this should be a reasonable and recommended value.
]
Heap size 2294K exceeds notification threshold (2048K)
-------------------------------------------------------------
These are warning messages that should not cause the program responsible for these errors to fail. They appear as a result of new event messaging mechanism and memory manager in 10g Release 2.
The meaning is that the process is just spending a lot of time in finding free memory extents during an allocate as the memory may be heavily fragmented. Fragmentation in memory is impossible to eliminate completely, however, continued messages of large allocations in memory indicate there are tuning opportunities on the application.
[ Note:- Set _kgl_large_heap_warning_threshold to a reasonable high value or zero to prevent these warning messages. Value needs to be set in bytes.
The default threshold in 10.2.0.1 is 2MB. So these messages could show up frequently in some application environments.
In 10.2.0.2, the threshold was increased to 50MB after regression tests, so this should be a reasonable and recommended value.
]
Friday, February 10, 2012
How can i delete oracle Database?
Solution:-
Dropping a database involves removing its datafiles, redo log files, control files, and initialization parameter files.
1) Use DBCA to Delete spacific Database.
2) Use "SQL> DROP DATABASE" Command .
The DROP DATABASE statement first deletes all control files and all other database files listed in the control file. It then shuts down the database instance.
To use the DROP DATABASE statement successfully, the database must be mounted in exclusive and restricted mode.
The DROP DATABASE statement has no effect on archived log files, nor does it have any effect on copies or backups of the database. It is best to use RMAN to delete such files. If the database is on raw disks, the actual raw disk special files are not deleted.
If you used the Database Configuration Assistant to create your database, you can use that tool to delete (drop) your database and remove the files.
Dropping a database involves removing its datafiles, redo log files, control files, and initialization parameter files.
1) Use DBCA to Delete spacific Database.
2) Use "SQL> DROP DATABASE" Command .
The DROP DATABASE statement first deletes all control files and all other database files listed in the control file. It then shuts down the database instance.
To use the DROP DATABASE statement successfully, the database must be mounted in exclusive and restricted mode.
The DROP DATABASE statement has no effect on archived log files, nor does it have any effect on copies or backups of the database. It is best to use RMAN to delete such files. If the database is on raw disks, the actual raw disk special files are not deleted.
If you used the Database Configuration Assistant to create your database, you can use that tool to delete (drop) your database and remove the files.
Tuesday, January 31, 2012
Where is the location of alert log file in oracle 11g ?
I got many question about this. its nothing different from oracle 10g.
just show the value of "background_dump_dest"
example:-
SQL>
SQL>
SQL> select * from v$version ;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL>
SQL>
SQL> show parameter background_dump_dest
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
background_dump_dest string g:\oracle11gr2\app\administrat
or\diag\rdbms\halimdb1g\halimd
b1g\trace
SQL>
so i will get my alert log in this loacation.
g:\oracle11gr2\app\administrator\diag\rdbms\halimdb1g\halimd b1g\trace
just show the value of "background_dump_dest"
example:-
SQL>
SQL>
SQL> select * from v$version ;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL>
SQL>
SQL> show parameter background_dump_dest
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
background_dump_dest string g:\oracle11gr2\app\administrat
or\diag\rdbms\halimdb1g\halimd
b1g\trace
SQL>
so i will get my alert log in this loacation.
g:\oracle11gr2\app\administrator\diag\rdbms\halimdb1g\halimd b1g\trace
Labels:
version
Subscribe to:
Posts (Atom)
My Blog List
-
-
-
Savepoint Funny3 months ago
-
-
-
-
-
-
-
-
-
Moving Sideways10 years ago
-
-
Upcoming Events...12 years ago
-