Connecting a Schema Holder at Startup
Progress supports connection parameters that you can use to connect the Progress schema holder and the ORACLE database. These parameters control how your system connects to a database. When the DataServer for ORACLE runs in a remote configuration, your startup command or parameter file must include parameters that control networking options.
Table 4–3 describes the connection parameters that relate to the remote DataServer and networking options.
Table 4–3: Remote DataServer Connection Parameters
Parameter
|
Description
|
Host Name (-H)
|
Indicates the name of the host machine in the network.
|
Network Type (-N)
|
Indicates the network type. TCP is the only possible value.
|
Service Name (-S)
|
Indicates the name of the service you are calling. The service you are calling is the broker on the host machine. Use the same name you used when you started the broker.
|
The following command starts Progress for NT or Windows:
- In single-user mode
- In a remote-DataServer configuration
- With a local schema holder connected
- With an ORACLE database connected
For example, the following command starts up Progress for Windows in a remote DataServer configuration, with a read-only schema holder and an ORACLE database connected.
Remote DataServer — NT or Windows Client
In this example, the schema holder’s physical name is oholder; it is read-only; the database type is ORACLE; the ORACLE database’s logical name is orademo; the host name is host1; the service name is oserviceA; the network type is TCP/IP; the user ID is scott; the password is tiger.
Local DataServer — NT or Windows
Remote DataServer — UNIX Client
Local DataServer — UNIX
Table 4–4 describes the parameters required for connecting to a schema holder and an ORACLE database.
Table 4–4: Required Connection Parameters
Parameter
|
Description
|
Internal Code Page (-cpinternal)
|
Specifies the name of the code page that Progress uses in memory. This code page must match the code page that the ORACLE database uses. Required when using a code page other than ibm850 or iso-1, such as in a DBE DataServer configuration.
|
Stream Code Page (-cpstream)
|
Specifies the name of the code page that Progress uses for stream I/O. This code page must match the code page that the ORACLE database uses. Required when using a code page other than ibm850 or iso-1, such as in a DBE DataServer configuration.
|
Password (-P)
|
Supplies the password that the DataServer for ORACLE uses to log into the ORACLE RDBMS.
|
Physical Database Name (-db)
|
For Progress databases, the string that follows this parameter is the physical name of the database you want to connect. However, for ORACLE databases, this physical database name can be any fill characters. For example, use the logical database name after the -db parameter or any other designation, such as oradb.
|
Single-user Mode (-1)
or
Read-only (-RO)
|
Specifies that a database is used in single-user mode. When you connect the schema holder, you must connect either in single-user mode or as read-only.
Specifies that a schema holder is read-only. Connecting a schema holder as read-only increases processing speed at compile time. It also allows multiple client processes on the same machine to access the schema holder without starting additional server processes.
|
User ID (-U)
|
Supplies the user ID that the DataServer for ORACLE uses to log into the ORACLE RDBMS.
SQL*Net and Net 8 allow you to pass the user ID and password as a single string to the -U parameter. If you specify -U userid/password@service-name , the USERID function returns the password information in addition to the user ID and service.
|
You can create a parameter file with the required parameters for each database. You can add more startup parameters than the ones listed-these are just the required parameters. For information on how to create a parameter file, see the Progress Startup Command and Parameter Reference.