Friday, August 10, 2007

We have already moved to

Please update your bookmarks.

indo-oracle admin

Read more!

Friday, March 23, 2007


DBNEWID is a database utility that can change the internal database identifier (DBID) and the database name (DBNAME) for an operational database

What Is the DBNEWID Utility?
Prior to the introduction of the DBNEWID utility, you could manually create a copy of a database and give it a new database name (DBNAME) by re-creating the control file. However, you could not give the database a new identifier (DBID). The DBID is an internal, unique identifier for a database. Because Recovery Manager (RMAN) distinguishes databases by DBID, you could not register a seed database and a manually copied database together in the same RMAN repository. The DBNEWID utility solves this problem by allowing you to change any of the following:
  • Only the DBID of a database
  • Only the DBNAME of a database
  • Both the DBNAME and DBID of a database
More read here
. ---.


Read more!

Wednesday, October 18, 2006

Links: Oracle Installation

Redhat dan Fedora Core
And here is the rest of it.

Read more!

Wednesday, October 11, 2006


Untuk yang menggunakan Oracle 10g R2, mungkin pernah mengalami hal dimana kita dapat dengan sukses connect menggunakan SQL*Plus, namun pada saat mencoba menjalankan aplikasi, kita kadang bisa connect kedatabase atau sama sekali tidak bisa terhubung dengan database.

Berikut ini mungkin bisa membantu mengatasi masalah anda.
  1. Set INBOUND_CONNECT_TIMEOUT_listener_name = 0 pada listener.ora
  2. Set SQLNET.INBOUND_CONNECT_TIMEOUT = 0 pada sqlnet.ora pada server
  3. Stop dan start database beserta dengan listernernya
  4. Test kembali aplikasi anda, apakah sudah berhasil connect ke database
Untuk melihat apakah nilai INBOUND_CONNECT_TIMEOUT pada listernet sudah berubah bisa dengan menggunakan:

LSNRCTL> show inbound_connect_timeout
LISTENER parameter "inbound_connect_timeout" set to 0
The command completed successfully

Berikut ada potongan dari keterangan error yang berhasil di kumpulkan.

-- alert.log pada database server
Wed Oct 11 16:42:35 2006
WARNING: inbound connection timed out (ORA-3136)
Wed Oct 11 16:43:25 2006
WARNING: inbound connection timed out (ORA-3136)
Wed Oct 11 16:48:32 2006
WARNING: inbound connection timed out (ORA-3136)
Wed Oct 11 16:54:20 2006
WARNING: inbound connection timed out (ORA-3136)

-- sqlnet.log pada aplikasi yg dijalankan
Fatal OSN connect error 12637, connecting to:

TNS for 32-bit Windows: Version - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows:
Version - Production
Time: 11-OCT-06 16:52:58
Tracing not turned on.
Tns error struct:
nr err code: 12206
TNS-12206: TNS:received a TNS error during navigation
ns main err code: 12637
TNS-12637: Packet receive failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0

Fatal OSN connect error 12547, connecting to:

TNS for 32-bit Windows: Version - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows:
Version - Production
Time: 11-OCT-06 16:52:58
Tracing not turned on.
Tns error struct:
nr err code: 12206
TNS-12206: TNS:received a TNS error during navigation
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 517
TNS-00517: Lost contact
nt secondary err code: 0
nt OS err code: 0

Use the SQLNET.INBOUND_CONNECT_TIMEOUT parameter to specify the time, in seconds, for a client to connect with the database server and provide the necessary authentication information.

If the client fails to establish a connection and complete authentication in the time specified, then the database server terminates the connection. In addition, the database server logs the IP address of the client and an ORA-12170: TNS:Connect timeout occurred error message to the sqlnet.log file. The client receives either an ORA-12547: TNS:lost contact or an ORA-12637: Packet receive failed error message.

. Without this parameter, a client connection to the database server can stay open indefinitely without authentication. Connections without authentication can introduce possible denial-of-service attacks, whereby malicious clients attempt to flood database servers with connect requests that consume resources.

To protect both the database server and the listener, Oracle Corporation recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying values for these parameters, consider the following recommendations:

Set both parameters to an initial low value.
Set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter.
For example, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed.

See Also:
Oracle9i Net Services Administrator's Guide for information about configuring these parameters



Others Resources:
  1. Oracle 10g - Troubleshooting Oracle Net Services
  3. oracle/manual-10gR2/network.102/b14212/

Read more!

Friday, June 16, 2006

Thrown when the IP address of a host cannot be determined

Pada saat installasi Oracle Client 10g Release 1 mungkin pernah ada yang mengalami error "Thrown when the IP address of a host cannot be determined" dan process berhenti pada saat "Processing Oracle Net Configuration Assistant 10…", hal ini terjadi pada computer yg terhubung ke jaringan dan menggunakan dynamic IP dari DHCP, sepertinya oracle installer mencoba untuk membaca ip address pada file hosts yang terdapat di folder %WINDIR%\system32\drivers\etc\. dan hanya mendapatkan entry localhost seperti terlihat sebagai berikut:    localhost

Nah solusinya yaitu dengan menambahkan entry baru berupa ip address yg didapat dari DHCP, ini dapat dilihat dengan menggunakan perintah "ipconfig /all" pada command prompt dan hasilnya akan terlihat seperti berikut:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix:
Description . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapter
Physical Address. . . . . . . : 00-0C-29-89-A6-FC
Dhcp Enabled. . . . . . . . . : Yes
Autoconfiguration Enabled . . : Yes
IP Address. . . . . . . . . . :
Subnet Mask . . . . . . . . . :
Default Gateway . . . . . . . :
DHCP Server . . . . . . . . . :
DNS Servers . . . . . . . . . :
Lease Obtained. . . . . . . . : Thursday, June 08, 2006 4:08:36 PM
Lease Expires . . . . . . . . : Thursday, June 08, 2006 10:08:36 PM

Dari atas terlihat ip address untuk computer yg digunakan adalah, maka tambahkan ip address tersebut pada file hosts, sehingga akan terlihat seperti berikut:       localhost vmware

Sekarang process installasi Oracle Client 10g Release 1 dapat dilanjutkan kembali dengan normal tanpa error.

Read more!

Thursday, April 20, 2006

Autotrace in SQLPLUS

From Thomas Kyte about autotrace:

Here is what I like to do to get autotrace working:
  • cd $oracle_home/rdbms/admin
  • log into sqlplus as system
  • run SQL> @utlxplan
  • run SQL> create public synonym plan_table for plan_table
  • run SQL> grant all on plan_table to public
  • exit sqlplus and cd $oracle_home/sqlplus/admin
  • log into sqlplus as SYS
  • run SQL> @plustrce
  • run SQL> grant plustrace to public
You can replace public with some user if you want. by making it public, you let anyone trace using sqlplus (not a bad thing in my opinion).

About Autotrace

You can automatically get a report on the execution path used by the SQL optimizer and the statement execution statistics. The report is generated after successful SQL DML (that is, SELECT, DELETE, UPDATE and INSERT) statements. It is useful for monitoring and tuning the performance of these statements. For complete articles please take a look at

Read more!

Tuesday, April 04, 2006

How to change database character set

Catat/backup nilai dari parameter sebelum melakukan perubahan, dengan tujuan agar apabila diinginkan dapat mengembalikan nilai parameter tersebut ke nilai awalnya.

show parameters JOB_QUEUE_PROCESSES;
show parameters AQ_TM_PROCESSES;

Kemudian dilanjutkan dengan process ALTER DATABASE untuk mengubah character set.


Jika dibutuhkan kita dapat mengubah kembali nilai dari JOB_QUEUE_PROCESSES dan AQ_TM_PROCESSES.

ALTER SYSTEM SET JOB_QUEUE_PROCESSES = old_job_queue_processes_value;
ALTER SYSTEM SET AQ_TM_PROCESSES = old_aq_tm_processes_value;

Dictionary Table
- select * from v$nls_parameters

Read more!

Monday, February 27, 2006

Oracle Database 10g Express Edition - Production

Oracle Database 10g Express Edition is now production and can be downloaded from OTN.

Oracle XE is an entry-level, small-footprint database based on the Oracle Database 10g Release 2 code base. It is free to develop, deploy, and distribute, fast to download and simple to administer.

Oracle Database XE can be installed on any size host machine with any number of CPUs, but it will store up to 4GB of user data, use up to 1GB of memory, and use one CPU on the host machine.

Read more!

Wednesday, February 01, 2006

Oracle Application Server 10g dan JDev 10g - Release Production

Production release 3 dari Oracle Application Server 10g dan JDeveloper 10g kini dapat didownload dari website OTN. ~.

Read more!

Thursday, January 12, 2006

Project Raptor Early Adopter Release 2 Downloads

January 11, 2006 oracle kembali me-release Project Raptor Early Adopter (v804) , release 2 ini bisa didownload langsung dari OTN. Sambil menunggu release production yg "mungkin" jauh lebih baik, anda dapat mencoba versi ini terlebih dahulu dan men-share kekurangan dan kelebihannya.

Read more!