November 24th 2011

error "OPatch cannot find a valid oraInst.loc file to locate Central Inventory" saat running opatch lsinventory

Error tersebut terjadi ketika akan menjalankan command opatch lsinventory untuk mengetahui patch yang sudah terinstall pada database.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
bash-3.2$ opatch lsinventory
Invoking OPatch 10.2.0.4.2
 
Oracle Interim Patch Installer version 10.2.0.4.2
Copyright (c) 2007, Oracle Corporation.  ALL rights reserved.
 
 
Oracle Home       : /export/home/users/oracle/product/10.2.0
Central Inventory : n/a
   FROM           : 
OPatch version    : 10.2.0.4.2
OUI version       : 10.2.0.4.0
OUI location      : /export/home/users/oracle/product/10.2.0/oui
Log file location : n/a
 
OPatch cannot find a valid oraInst.loc file TO locate Central Inventory.
 
OPatch failed WITH error code 104

Hal ini terjadi karena file oraInst.loc tidak ditemukan di direktori /etc/.

Solusi untuk memperbaikinya yaitu dengan mengcopy file oraInst.loc ke folder /etc atau bisa juga dengan set inventory location file oraInst tersebut

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
bash-3.2$ opatch lsinventory -invPtrLoc /export/home/users/oracle/product/10.2.0/oraInst.loc 
Invoking OPatch 10.2.0.4.2
 
Oracle Interim Patch Installer version 10.2.0.4.2
Copyright (c) 2007, Oracle Corporation.  ALL rights reserved.
 
 
Oracle Home       : /export/home/users/oracle/product/10.2.0
Central Inventory : /export/home/users/oracle/oraInventory
   FROM           : /export/home/users/oracle/product/10.2.0/oraInst.loc
OPatch version    : 10.2.0.4.2
OUI version       : 10.2.0.4.0
OUI location      : /export/home/users/oracle/product/10.2.0/oui
Log file location : /export/home/users/oracle/product/10.2.0/cfgtoollogs/opatch/opatch2011-11-24_17-14-40PM.log
 
Lsinventory Output file location : /export/home/users/oracle/product/10.2.0/cfgtoollogs/opatch/lsinv/lsinventory2011-11-24_17-14-40PM.txt
 
--------------------------------------------------------------------------------
Installed Top-level Products (2): 
 
Oracle DATABASE 10g                                                  10.2.0.1.0
Oracle DATABASE 10g Release 2 Patch SET 3                            10.2.0.4.0
There are 2 products installed IN this Oracle Home.
 
 
Interim patches (41) :
 
Patch  9442339      : applied ON Tue Jan 18 19:10:20 WIT 2011
   Created ON 18 Mar 2010, 11:29:52 hrs PST8PDT
   Bugs fixed:
     8210889, 8479537, 9442339, 6923450
 
Patch  9442335      : applied ON Tue Jan 18 19:10:14 WIT 2011
   Created ON 18 Mar 2010, 11:29:50 hrs PST8PDT
   Bugs fixed:
     9442335
 
Patch  9442331      : applied ON Tue Jan 18 19:10:12 WIT 2011
   Created ON 18 Mar 2010, 11:29:48 hrs PST8PDT
   Bugs fixed:
     9442331
 
Patch  9442328      : applied ON Tue Jan 18 19:10:09 WIT 2011
   Created ON 18 Mar 2010, 11:29:46 hrs PST8PDT
   Bugs fixed:
     9442328
 
Patch  9352191      : applied ON Tue Jan 18 19:10:06 WIT 2011
   Created ON 18 Mar 2010, 11:29:43 hrs PST8PDT
   Bugs fixed:
     8534387, 8290506, 7375644, 9352191, 7150470, 7592346, 9119226, 8836308
 
Patch  9173253      : applied ON Tue Jan 18 19:10:03 WIT 2011
   Created ON 2 DEC 2009, 22:44:53 hrs PST8PDT
   Bugs fixed:
     9173253
 
Patch  9173248      : applied ON Tue Jan 18 19:10:00 WIT 2011
   Created ON 2 DEC 2009, 22:44:51 hrs PST8PDT
   Bugs fixed:
     9173248
 
Patch  9173244      : applied ON Tue Jan 18 19:09:55 WIT 2011
   Created ON 2 DEC 2009, 22:44:50 hrs PST8PDT
   Bugs fixed:
     9173244
 
Patch  8836686      : applied ON Tue Jan 18 19:09:51 WIT 2011
   Created ON 1 Sep 2009, 10:39:13 hrs PST8PDT
   Bugs fixed:
     8836686
 
Patch  8836684      : applied ON Tue Jan 18 19:09:48 WIT 2011
   Created ON 1 Sep 2009, 10:39:11 hrs PST8PDT
   Bugs fixed:
     8836684
 
Patch  8836683      : applied ON Tue Jan 18 19:09:45 WIT 2011
   Created ON 1 Sep 2009, 10:39:09 hrs PST8PDT
   Bugs fixed:
     8309623, 8836683
 
Patch  8836681      : applied ON Tue Jan 18 19:09:42 WIT 2011
   Created ON 1 Sep 2009, 10:39:07 hrs PST8PDT
   Bugs fixed:
     8836681, 8309587
 
Patch  8836678      : applied ON Tue Jan 18 19:09:37 WIT 2011
   Created ON 1 Sep 2009, 10:39:06 hrs PST8PDT
   Bugs fixed:
     8836678
 
Patch  8836677      : applied ON Tue Jan 18 19:09:34 WIT 2011
   Created ON 11 Sep 2009, 01:14:30 hrs PST8PDT
   Bugs fixed:
     8836677
 
Patch  8836675      : applied ON Tue Jan 18 19:09:30 WIT 2011
   Created ON 1 Sep 2009, 10:39:01 hrs PST8PDT
   Bugs fixed:
     8309637, 8836675
 
Patch  8836671      : applied ON Tue Jan 18 19:09:27 WIT 2011
   Created ON 1 Sep 2009, 10:39:01 hrs PST8PDT
   Bugs fixed:
     8836671
 
Patch  8836667      : applied ON Tue Jan 18 19:09:25 WIT 2011
   Created ON 1 Sep 2009, 10:38:59 hrs PST8PDT
   Bugs fixed:
     8836667
 
Patch  8568405      : applied ON Tue Jan 18 19:09:22 WIT 2011
   Created ON 8 Jun 2009, 20:04:47 hrs PST8PDT
   Bugs fixed:
     8568405
 
Patch  8568404      : applied ON Tue Jan 18 19:09:17 WIT 2011
   Created ON 8 Jun 2009, 20:04:46 hrs PST8PDT
   Bugs fixed:
     8568404
 
Patch  8568402      : applied ON Tue Jan 18 19:09:14 WIT 2011
   Created ON 8 Jun 2009, 20:04:44 hrs PST8PDT
   Bugs fixed:
     6870937, 8568402
 
Patch  8568398      : applied ON Tue Jan 18 19:09:09 WIT 2011
   Created ON 25 Jun 2009, 12:05:00 hrs PST8PDT
   Bugs fixed:
     6392076, 8568398
 
Patch  8568397      : applied ON Tue Jan 18 19:09:01 WIT 2011
   Created ON 8 Jun 2009, 20:04:39 hrs PST8PDT
   Bugs fixed:
     8568397
 
Patch  8568395      : applied ON Tue Jan 18 19:08:58 WIT 2011
   Created ON 8 Jun 2009, 20:04:38 hrs PST8PDT
   Bugs fixed:
     8309639, 8568395
 
Patch  8309642      : applied ON Tue Jan 18 19:08:55 WIT 2011
   Created ON 24 Mar 2009, 12:34:40 hrs PST8PDT
   Bugs fixed:
     8309642
 
Patch  8309632      : applied ON Tue Jan 18 19:08:52 WIT 2011
   Created ON 24 Mar 2009, 12:34:37 hrs PST8PDT
   Bugs fixed:
     8309632
 
Patch  8309592      : applied ON Tue Jan 18 19:08:48 WIT 2011
   Created ON 24 Mar 2009, 12:34:34 hrs PST8PDT
   Bugs fixed:
     8309592
 
Patch  7609058      : applied ON Tue Jan 18 19:08:44 WIT 2011
   Created ON 31 DEC 2008, 04:15:23 hrs PST8PDT
   Bugs fixed:
     7609058
 
Patch  7609057      : applied ON Tue Jan 18 19:08:40 WIT 2011
   Created ON 31 DEC 2008, 04:17:07 hrs PST8PDT
   Bugs fixed:
     7609057
 
Patch  7375617      : applied ON Tue Jan 18 19:08:37 WIT 2011
   Created ON 16 Sep 2008, 01:15:59 hrs PST8PDT
   Bugs fixed:
     7375617
 
Patch  7375613      : applied ON Tue Jan 18 19:08:34 WIT 2011
   Created ON 16 Sep 2008, 01:15:57 hrs PST8PDT
   Bugs fixed:
     7375613
 
Patch  7375611      : applied ON Tue Jan 18 19:08:31 WIT 2011
   Created ON 16 Sep 2008, 01:15:53 hrs PST8PDT
   Bugs fixed:
     7375611
 
Patch  7197583      : applied ON Tue Jan 18 19:08:27 WIT 2011
   Created ON 3 Jul 2008, 02:11:22 hrs PST8PDT
   Bugs fixed:
     7197583
 
Patch  7155254      : applied ON Tue Jan 18 19:08:22 WIT 2011
   Created ON 3 Jul 2008, 02:10:57 hrs PST8PDT
   Bugs fixed:
     7155254
 
Patch  7155253      : applied ON Tue Jan 18 19:07:35 WIT 2011
   Created ON 3 Jul 2008, 02:10:55 hrs PST8PDT
   Bugs fixed:
     7155253
 
Patch  7155252      : applied ON Tue Jan 18 19:06:57 WIT 2011
   Created ON 3 Jul 2008, 02:10:54 hrs PST8PDT
   Bugs fixed:
     7155252
 
Patch  7155251      : applied ON Tue Jan 18 19:06:52 WIT 2011
   Created ON 3 Jul 2008, 02:10:52 hrs PST8PDT
   Bugs fixed:
     7155251
 
Patch  7155250      : applied ON Tue Jan 18 19:06:47 WIT 2011
   Created ON 3 Jul 2008, 02:10:51 hrs PST8PDT
   Bugs fixed:
     7155250
 
Patch  7155249      : applied ON Tue Jan 18 19:06:43 WIT 2011
   Created ON 3 Jul 2008, 02:10:48 hrs PST8PDT
   Bugs fixed:
     7155249
 
Patch  7155248      : applied ON Tue Jan 18 19:06:40 WIT 2011
   Created ON 3 Jul 2008, 02:10:38 hrs PST8PDT
   Bugs fixed:
     7155248
 
Patch  7385253      : applied ON Tue Jan 18 19:06:02 WIT 2011
   Created ON 29 Sep 2008, 02:36:11 hrs PST8PDT
   Bugs fixed:
     7385253
 
Patch  5523375      : applied ON Tue Jan 18 19:05:46 WIT 2011
   Created ON 3 Jul 2008, 04:08:44 hrs PST8PDT
   Bugs fixed:
     5523375
 
 
 
--------------------------------------------------------------------------------
 
OPatch succeeded.

Incoming search terms:

  • opatch cannot find a valid orainst loc file to locate central inventory
  • opatch failed with error code 39
  • opatch failed with error code 160
  • opatch failed with error code 106
  • opatch failed with error code 135
  • opatch failed with error code 104
  • opatch failed with error code 130
  • opatch failed with error code = 39
  • opatch failed with error code 139
  • opatch failed with error code 115

No Comments yet »

June 18th 2011

alert "ORA-02019 : connection description for remote database not found" on alert log

Problem : Selalu muncul error ORA-02019 : connection description for remote database not found di alert log. Sebelumnya memang terdapat dblink ke database lain tetapi itupun sudah di drop dan tidak ada stored procedure yang mengarah/menggunakan dblink sama sekali.

Alert log :

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Thread 1 advanced TO log SEQUENCE 9592
CURRENT log# 3 seq# 9592 mem# 0: /oradata/emrep/emrep/redo03.log
Thu Jun 16 13:30:34 2011
Errors IN file /oracle/app/admin/emrep/bdump/emrep_reco_3230.trc:
ORA-02019: connection description FOR remote DATABASE NOT found
Thu Jun 16 13:30:34 2011
Errors IN file /oracle/app/admin/emrep/bdump/emrep_reco_3230.trc:
ORA-02019: connection description FOR remote DATABASE NOT found
Thu Jun 16 13:30:34 2011
Errors IN file /oracle/app/admin/emrep/bdump/emrep_reco_3230.trc:
ORA-02019: connection description FOR remote DATABASE NOT found
Thu Jun 16 14:17:18 2011
Errors IN file /oracle/app/admin/emrep/bdump/emrep_reco_3230.trc:
ORA-02019: connection description FOR remote DATABASE NOT found
Thu Jun 16 14:17:18 2011
Errors IN file /oracle/app/admin/emrep/bdump/emrep_reco_3230.trc:
ORA-02019: connection description FOR remote DATABASE NOT found
Thu Jun 16 14:17:18 2011
Errors IN file /oracle/app/admin/emrep/bdump/emrep_reco_3230.trc:
ORA-02019: connection description FOR remote DATABASE NOT found

Penyebab : Hal ini dikarenakan terdapat transaksi yang masih gantung yang merefer ke database link padahal database linknya sendiri sudah tidak ada.

Solusi : Check table dba_2pc_pending.

1
SQL> SELECT LOCAL_TRAN_ID,GLOBAL_TRAN_ID,STATE,MIXED,COMMIT# FROM DBA_2PC_PENDING;

Ambil nilai local tran_id lalu purging transaksi tersebut menggunakan package DBMS_TRANSACTION.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
SQL> conn /AS sysdba
Connected.
SQL> EXECUTE DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY('21.27.30277');
 
PL/SQL PROCEDURE successfully completed.
 
SQL> COMMIT;
 
Commit complete.
 
SQL> EXECUTE DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY('3.18.124253');
 
PL/SQL PROCEDURE successfully completed.
 
SQL> COMMIT;
 
Commit complete.
 
SQL> EXECUTE DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY('15.42.11902');
 
PL/SQL PROCEDURE successfully completed.
 
SQL> COMMIT;
 
Commit complete.

Check alert log lagi beberapa saat, maka error tersebut tidak akan muncul sama sekali.

Incoming search terms:

  • ora-02019: connection description for remote database not found
  • ora-02019 connection description for remote database not found
  • ora-02019
  • ora-02019 connection description for remote database in alert log

2 Comments »

May 7th 2011

ORA-12162: TNS:net service name is incorrectly specified

Problem : Error ORA-12162:TNS: net service name is incorrectly specified ketika akan mengakses database menggunakan sqlplus.

Permasalahan : Hal ini terjadi karena setting ORACLE_SID belum di set pada session user oracle tersebut.

Solusi : export ORACLE_SID=nama_instance atau jalankan oraenv.

Sebagai tambahan, setting juga ORACLE_SID, ORACLE_HOME, PATH di user profile oracle agar ketika kita masuk sebagai user oracle setting tersebut sudah langsung otomatis terexport.

Contoh setting oracle path yang harus ditambahkan di user profile oracle :

1
2
3
4
export ORACLE_SID=orcl
export ORACLE_HOME=/u01/oracle/app/10.2.0/db_1
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$ORACLE_HOME/bin:/bin:/usr/bin:/usr/LOCAL/bin

Incoming search terms:

  • ora-12162: tns:net service name is incorrectly specified

No Comments yet »

February 24th 2011

Private Strand Flush Not Complete

Kejadian :

Ketika cek alert log, muncul error Private strand flush not complete.

bash-3.00$ tail -f alert_nldapdb.log

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Thread 1 cannot allocate NEW log, SEQUENCE 18242
Private strand FLUSH NOT complete
  CURRENT log# 4 seq# 18241 mem# 0: /oradata1/ldap/ldapdb/redo04.log
  CURRENT log# 4 seq# 18241 mem# 1: /oradata6/ldap/ldapdb/redo04_b.log
Thread 1 advanced TO log SEQUENCE 18242
  CURRENT log# 5 seq# 18242 mem# 0: /oradata1/ldap/ldapdb/redo05.log
  CURRENT log# 5 seq# 18242 mem# 1: /oradata6/ldap/ldapdb/redo05_b.log
Thu Feb 24 07:34:31 2011
Thread 1 cannot allocate NEW log, SEQUENCE 18243
Private strand FLUSH NOT complete
  CURRENT log# 5 seq# 18242 mem# 0: /oradata1/ldap/ldapdb/redo05.log
  CURRENT log# 5 seq# 18242 mem# 1: /oradata6/ldap/ldapdb/redo05_b.log
Thread 1 advanced TO log SEQUENCE 18243
  CURRENT log# 6 seq# 18243 mem# 0: /oradata1/ldap/ldapdb/redo06.log
  CURRENT log# 6 seq# 18243 mem# 1: /oradata6/ldap/ldapdb/redo06_b.log

Penyebab :

Hal ini terjadi ketika belum selesai menulis informasi ke redo log lalu proses mencoba untuk switch redo log. Gejalanya sama seperti checkpoint not complete, switch log tidak dapat dilakukan sampai semua redo selesai ditulis ke dalam redo log.

Solusi :

Error tersebut tidak perlu menjadi concern utama karena hal tersebut bukan merupakan bugs, perlu diperhatikan terkait disk tempat penyimpanan archive, disamping itu besar dari redolog.

Info lebih detail bisa membaca notes metalink 372557.1

Incoming search terms:

  • Private strand flush not complete 11g
  • Private strand flush not complete
  • private strand flush not complete 11gr2
  • private strand flush not complete in 11g
  • private strand flush not complete in oracle 11g
  • oracle private strand flush not complete 11g
  • oracle 11g private strand flush not complete
  • enterprise manager Private strand flush not complete
  • private strand flush
  • private strand flush not complete oracle

No Comments yet »

January 26th 2011

Opatch problem : ApplySession failed: ApplySession failed in system modification phase... 'Verification of patch failed: null'

Problem : Kemarin saat akan melakukan patching database versi 10.2.0.3 untuk menambal bugs ORA-600 : kcbso1_1 terdapat problem failed mereplace file eksisting. Errornya sendiri sebagai berikut :

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Verifying the UPDATE...
Inventory CHECK OK: Patch ID 6110331 IS registered IN Oracle Home inventory WITH proper meta-DATA.
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcl.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbt.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbl.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcb.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbz.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbb.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbw.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbk.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbs.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbm.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbv.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbr.o"
Archive failed: failed TO UPDATE "/oracle/app/product/10.2.0/db_1/lib/libserver10.a" WITH updated "/export/home/oracle/mii/opatch/6110331/files/lib/libserver10.a/kcbo.o"
 
ApplySession failed: ApplySession failed IN system modification phase... 'Verification of patch failed: null'
OPatch will attempt TO restore the system...
Restoring the Oracle Home...
Checking IF OPatch needs TO invoke 'make' TO restore SOME binaries...
OPatch was able TO restore your system. Look at log file AND TIMESTAMP OF each file TO make sure your system IS IN the state prior TO applying the patch.
 
OPatch failed WITH error code 73

Solusi : Berdasarkan referensi dari document metalink OPatch Failing Validation Phase When Archiving Really Did Not Fail (Doc ID 353150.1), diperoleh informasi bahwa hal ini disebabkan karena belum diinstallnya patch 123908-1 pada solaris. Size file eksisting berbeda ukuruannya dengan file source opatch (lebih besar 4 kb).

Setelah diinstall patch solaris, akhirnya patch database bisa berjalan dengan lancar dan sukses.

No Comments yet »

Next »