Initializing SAP Connect 
Use
You can use SAPDBA for Oracle to initialize SAP connect, which you normally do during database installation. You can do this with the SAPDBA menus, as described here, or with the
SAPDBA command init_sap_connect.
Prerequisites
You have configured and started SAPDBA. Refer to
Getting Started with SAPDBA.
If you use the SAPDBA menus, you can set the
sapsid
switch (see below) when you start SAPDBA, as follows:
sapdba -sapsid <SID1>,<SID2>,...
Procedure
Choose User and security ®
Initialize SAP Connect.
SAPDBA displays what it does if you continue.
Choose whether you want to continue and initialize SAP connect.
Result
The result described below refers to both the command line and the menu execution of this function.
SAPDBA does the following when you initialize SAP connect:
remote_os_authent
in the file
init<ORACLE_SID>.ora
is
not set, SAPDBA sets it to
remote_os_authent = true
.
- SAPDBA performs a series of actions for the following database users, depending on whether the
sapsid
switch is set or not:
sapsid
is
not set, for the
SAPR3
user and system ID
ORACLE_SID
If
sapsid
is set, for the users
SAP<SID1>
,
SAP<SID2> ...
and system IDs
<SID1>
,
<SID2> ...
.
The system ID is represented by the variable
<SID>
below. Remember that, if the
sapsid
switch is set, there can be multiple users, schemas, and tables.SAPDBA performs the following actions:
- If not already present, SAPDBA creates the users specified above, that is, either
SAPR3
or
SAP<SID1>
,
SAP<SID2> ...
The initial passwords for the new users are set to
SAP
.
SAPDBA deletes the schemas
OPS$<SID>ADM
and all associated tables (this should only affect the
SAPUSER
tables).
SAPDBA recreates the schemas
OPS$<SID>ADM
without password, that is, they are identified at operating system level using the operating system user
<SID>ADM
.
SAPDBA recreates the tables
OPS$<SID>ADM.SAPUSER
and enters the
SAPR3
or the
SAP<SID>
users in encrypted form (starting with Release 4.5B) under
SAPR3-CRYPT
or
SAP<SID>-CRYPT
in the tables.