For: Bug Trace
When: If you got a bug issued in production env, we can't not launch IUI for debuging, and we have to trace the bug according to the data in the database or the log in the server. In term of handling that, we need access production env.
Note: DO NOT do any operation to update/create record/file in production env. What we CAN do is only to read log file and execute inquiry sql.
1. Access Prodcution DB
. Copy the following string into your tnsname.ora which is located in your oracle client directory.
# For Production Array
InnoProdAry =
(DESCRIPTION =
# (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.12.1)(PORT = 1521))
# )
(CONNECT_DATA =
(SID = PT0A11)
(SERVER = DEDICATED)
)
)
# For Production CELL
InnoProdCel =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.12.2)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = pcel1)
(INSTANCE_NAME = pcel12)
)
)
# For Production CF
InnoProdCF =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.16.12.3)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = pcft13)
)
)
. Login Production DB
ARRAY line: username/pwd: aryuser/aryuser
CELL line: username/pwd: celuser/celuser
CF line: username/pwd: cftuser/cftuser
.Execute SQL in Production DB
After login the db, you can execute sql to hunt the information you are interested.
ARRAY line: add prefix, ary0, before the table name in your sql.
CELL line: needn't add any prefix before the table name in you sql. Might by a mistaken setting by DBA :).
CF line: add prefix, cft, before the table name in your sql.
2. Access Production servers
Array line: hostname: 172.16.12.11 user/pwd: arymes/123456
Cell line: hostname: 172.16.12.13 user/pwd: celmes/123456
CF line: hostname: 172.16.12.15 user/pwd: cftmes/123456