Skip Headers
Oracle® Transparent Gateway for DB2/400 Installation and User's Guide
10g Release 2 (10.2) for IBM iSeries OS/400

Part Number B16222-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

A Oracle Net Files and Members

This appendix lists and defines the member names in the LOG, ORA, and TRC gateway library files

This appendix contains the following sections:

A.1 File Members

Members are listed for the following file types:

A.1.1 LOG File Members

The LOG file contains the LISTENER member, which is the default log output member for the Oracle Net TCP/IP listener.

To display this member on the AS/400, use the following command:

WRKMBRPDM instance_name/LOG

where instance_name is the name that is used for the gateway when it is installed.

In the LOG file, which is in the instance library, the LISTENER member records information about the startup of the listener and also records information about every connection attempt that is made to the associated instance. The file can get quite large over time, and you should therefore occasionally clear out the LISTENER member entries by using the CLRPFM FILE command. To issue the command, you need to sign on to your iSeries computer with either the QSECOFR ID or the instance ID and then enter the following command:

CLRPFM FILE(instance_name/LOG) MBR(LISTENER)

The LISTENER member can also be displayed using the WRKTRCLOG command. The gateway instance library should be in the library list when you use the WRKTRCLOG command.

A.1.2 ORA File Members

The ORA file contains the following members:

A.1.2.1 LISTENER

Member LISTENER contains the parameter values for the listener. The values in this file should not be changed directly with an AS/400 editor. The most commonly used parameters can be changed with the CHGORANET command. All other values must be changed in the ORA(LISTENER_CHG) file. Refer to "CHGORANET, Change Network Parameters" for more information.

A.1.2.2 LISTENER_CHG

Member LISTENER_CHG is used to make changes to the ORA(LISTENER) file. Refer to "CHGORANET, Change Network Parameters" for more information.

A.1.2.3 LISTENLOCK

Member LISTENLOCK is the ORA(LISTENLOCK) member. It is used to ensure that only one instance of the RUNORALSN program is running. The RUNORALSN program runs the TCP/IP listener. Do not modify this file.

A.1.2.4 SQLNET

Member SQLNET contains the network parameter values for Oracle Net. The values in this file should not be changed directly with an AS/400 editor. The most commonly used parameters can be changed with the CHGORANET command. All other values must be changed in the ORA(SQLNET_CHG) file. Refer to "CHGORANET, Change Network Parameters" for more information.

A.1.2.5 SQLNET_CHG

Member SQLNET_CHG is used to make changes to the ORA(SQLNET) file. Refer to "CHGORANET, Change Network Parameters" for more information.

A.1.2.6 Displaying File Members

To display these members on the AS/400, use the following command:

WRKMBRPDM instance_name/ORA

where instance_name is the name that is used for the gateway when it is installed. You may also use the command WRKTRCLOG, but you must first make sure that the instance library is in the library list before using this command.

A.1.3 TRC File Members

The TRC file contains the following members, where xxxxxx is numeric (the job number):

  • LISTxxxxxx is the default trace output file for the Oracle Net TCP/IP listener, where xxxxxx is the job number of the listener.

  • SERVxxxxxx is the Oracle Net trace for server job number xxxxxx.

To display these members on the AS/400, use the following AS/400 command:

WRKMBRPDM instance_name/TRC

where instance_name is the name that is used for the gateway when it is installed. Alternatively, you may use the command WRKTRCLOG, but you must first make sure that the instance library is in the library list before using this command.

A.1.4 ORA files in the Integrated File System (IFS)

There is a .ORA file, CALL_NAMES.ORA, in the IFS. This file is used in conjunction with DB2/400 SQL User Defined Functions (UDF) that are to be called through the gateway. Oracle must be aware of all the DB2/400 UDFs. An attempt to use a UDF that does not appear in this file will result in an ORA-06571 error. The file is located at /home/myinst/rdbms/admin/call_names.ora where 'myinst' is the name of your gateway instance. The file may be edited with the EDTF system editor. The names of the UDFs are found in this file, at most one name in each line. The name may be qualified by the name of the library in which a UDF resides, e.g., "MYORAINST.MYFUNC".

A.2 Agent Trace Files

Agent trace files are now located within the integrated file system in the directory /home/myinst/rdbms/log, where myinst is the instance name. The file names are of the form myinst_agt_nnnnnn.trc, where myinst is the instance name, and nnnnnn is the job number. To display these files, use the WRKTRCLOG command, but ensure that the instance library is in the library list before doing so.