2
Console Configuration

This chapter discusses getting started with Oracle Enterprise Manager and configuring the Console when it is running under Microsoft Windows NT or Windows 95.

• Setting Up the Repository User Account on page 2-2
• Creating a Repository on page 2-5
• Starting Oracle Enterprise Manager on page 2-7
• Discovering Network Services on page 2-8
• Enterprise Manager Console and Oracle Names on page 2-10
• Starting Enterprise Manager DBA Applications on page 2-11
• Setting Preferences on page 2-12
• Configuring a Remote Database for Backup or SYSDBA Administration on page 2-13
• Recovery Catalog Setup and Registration for Oracle8 on page 2-16
• Encoding Japanese Characters When Sending Email on page 2-20
• Troubleshooting on page 2-21

 

Note:  Please check the Oracle Enterprise Manager Readme for the compatibility matrix. The readme is located in the ORACLE_HOME/SYSMAN/ADMIN directory.

   

Setting Up the Repository User Account

Before you start the Enterprise Manager, you must set up the repository user account. A repository is a set of tables in an Oracle database which stores data and information required by the Oracle Enterprise Manager Console. The tables are owned by the account that creates them.

You need to have an Oracle user account with DBA (Database Administrator) privileges set up on the database where the repository will be created. Each DBA must have their own repository for the nodes they are responsible for. The repository account can be located in any Oracle database that is accessible on the network.

Please check the Oracle Enterprise Manager Readme for the compatibility matrix. The readme is located in the $ORACLE_HOME\SYSMAN\ADMIN directory.

Create a Separate Tablespace for the Repository

Oracle recommends that you create a separate tablespace for the Oracle Enterprise Manager repository.

1. Start Storage Manager.
2. Login to connect to an existing account on the database with system (DBA) privileges.
3. Select Create from the Tablespace menu. The Create Tablespace property sheet appears.
4. In the Name field, type OEMREP as the name of the new tablespace.
5. Click the Add button in the Datafiles section. The Create Datafile property sheet appears, allowing you to specify a new datafile which will belong to the new tablespace.
6. In the Name field, type in complete path and name of the datafile. For example: c:\orant\database\oemrep01.dbf.
7. In the Size section, enter the size of the new datafile where the size is calculated using the following formula:

20M + DB_BLOCK_SIZE


For example, assuming a 2K database block size, the file size should be 20482K.


For the calculation, convert values to bytes; then, convert bytes to kbytes:


((20 * 1048576) + (2048)) / 1024 = 20482


1048576 is the number of bytes in a Megabyte

8. Click the OK button in the Create Datafile property sheet.
9. In the Extents Page, select Override Default Values and fill in the following information:

Initial Size: 32K


Next Size: 128K


Increase Size By: 0


Maximum Number:

Select Unlimited if you are using Oracle 7.3 or later.


Select Value if you are using a version prior to Oracle 7.3. Specify a value that is 75% of the maximum number of extents per segment as enforced by DB_BLOCK_SIZE.


For example:

 

DB_BLOCK_SIZE	Enforced Maximum	Recommended Value
2K	121	90
4K	249	186
8K	505	378
16K	1017	762
32K	2041	1530

   

10. Click the Create button in the Create Tablespace property sheet.

Create a User

To set up a user account with DBA privileges, follow the procedure below:

1. Start Security Manager.
2. Login to connect to an existing account on the database with system (DBA) privileges.
3. Choose Create from the User menu. The Create User property sheet appears.
4. In the General Page, fill in the following information:

In the Name field, enter a name for the new user.


In the Password and Confirm Password fields, enter a password.


Choose OEMREP as the default tablespace.


Choose a tablespace that is dedicated to temporary segments as the user's temporary tablespace. In order to optimize sort performance, when running Oracle 7.3 or later, ensure this tablespace has been defined with the TEMPORARY keyword. For example, temporary_data.

5. In the Roles/Privileges Page, fill in the following information:

Choose Role as the Privilege Type.


Grant the DBA role to the user.

6. Click the Create button after specifying the requisite parameters.

When you start Oracle Enterprise Manager, connect to the repository database with this user account. The repository will automatically be generated.

 

Note:  Beginning with Oracle Enterprise Manager version 1.3.5, a new repository will be created for every new user login. One user can use one repository at one time.

   

Creating a Repository

The Repository Manager Wizard is started when you select Repository Manager in the Oracle Enterprise Manager program group.
 

Note:  You need to have an Oracle user account with DBA (Database Administrator) privileges in order to use the Oracle Repository Manager.

   

The Repository Manager allows you to choose from the following operations:

Operation	Description
Create/validate Enterprise Manager repositories	During the create/validate process, Repository Manager upgrades an existing repository or creates a new one if one does not already exist. If you drop a repository, the information contained in the repository is lost.
Drop Enterprise Manager repositories	If the database objects for the repository component exist, they will be deleted.
Save a list of the discovered nodes	You can choose to save a list of the discovered nodes in an existing repository to a text file. Specify the name, such as discnode.txt, and location of the file where you want to save the list of discovered node names. The default location is the ORACLE_HOME\BIN directory.  The text file can be loaded into the Add Nodes page of the Discover New Services wizard.

 

You can choose the repository components that you want to create, validate, or drop. The Oracle Diagnostics Pack, Oracle Tuning Pack, and the Oracle Change Management Pack are dependent on the Oracle Enterprise Manager repository. Because of this dependency, a selection may be automatically checked and grayed out when another option is selected. For example, if you choose to create a Tuning Pack repository, the Oracle Enterprise Manager option is automatically selected because it is required.

When you choose Drop, Oracle Enterprise Manager is selected by default. The Oracle Diagnostics Pack, Oracle Tuning Pack, and the Oracle Change Management Pack are also selected because that repository cannot exist without the Oracle Enterprise Manager repository. If you want to drop only a specific pack's repository, remove the check on the Oracle Enterprise Manager repository; then, check the option for the pack you would like to remove.

The last page of the wizard allows you to enter the login information for the repository where the operation you have requested will be performed. The process takes a few minutes to complete.

All repository objects which are required by a particular tool will be created the first time the tool is started. Alternatively, the user can go into the repository and create all the repository objects at once.

If you have an existing repository from a previous release of Oracle Enterprise Manager, check for compatibility:

• If your Oracle Enterprise Manager repository is older than your Oracle Enterprise Manager Console, the existing repository is automatically upgraded when you log into the repository.
• If your Oracle Enterprise Manager Console is older than your Oracle Enterprise Manager repository, you must install a more recent compatible version of the Oracle Enterprise Manager. The console will detect this situation and inform you of the console version that is required.

If there is an unexpected failure during a repository upgrade, the repository will need to be recreated. To prevent having to recreate repositories at a future date, Oracle recommends that you save your repository. Saving the repository protects the user's manually entered information, such as events, jobs, and preferred credentials, as well as collected information for products such as Oracle Expert and Trace.

Repositories can be saved by doing a full cold backup (take the database off-line and copy datafiles to storage) or by exporting the user.

Starting Oracle Enterprise Manager

To start the Enterprise Manager Console, select Oracle Enterprise Manager from the Oracle Enterprise Manager folder on the Start Menu. 

Note:  Only one instance of the Oracle Enterprise Manager Console can be run on a machine. However, you can run multiple instances of the DBA tools. Oracle Enterprise Manager is not supported to be run from a remote machine. It is only supported if run locally. Shared installs of the console are not supported.

   

Connecting to a Repository

Oracle Enterprise Manager requires unique usernames across all repositories whether or not the repositories are in different databases, because:

• The Intelligent Agents use the unique username when tracking jobs and events.
• The username is associated with the Console location when creating a return address for notifications.

The process for connecting to a repository is outlined below.

1. Enterprise Manager started.
2. The copyright window displays, then, the Login Information dialog box appears.
3. Through the Login Information dialog box, the user connects to the user account in the Oracle database where this Enterprise Manager repository is stored.
4. The Console looks up the repository associated with his username.

If the repository does not exist, it is automatically created and a dialog box informs you of the operation. 

Note:  You should not log on to the Console repository multiple times with the same username. A warning displays if you attempt this. You should only ignore the warning if the previous Console session was aborted or a machine was disconnected. When a username is logged in multiple times, agent notifications are sent to the most recent login.

   

Discovering Network Services

The Oracle Enterprise Manager Console must discover network services, such as databases, listeners, and nodes, to populate the Navigator tree, in order to manage these services for the Job Scheduling and Event Management systems.

The Navigator's Service Discovery feature provides wizards for identifying network services and populating the Navigator tree.

To begin discovering services, your Oracle networking system must be properly installed. Methods of discovering services are listed below:

Method	Function	For Agent Version
Discover New Services Wizard	Discovers new nodes and the services on the nodes.	Intelligent Agent release 7.3.3 or higher using the TCP/IP protocol
Refresh Services Wizard	Refreshes and retries discovery on nodes	Intelligent Agent release 7.3.3 or higher using the TCP/IP protocol
Manually Define Services Wizard	Enables you to manually enter information about services on nodes	Does not have an Oracle Intelligent Agent or has a pre-7.3.3 Oracle Intelligent Agent
Discovery with topo_ops.ora file	Manual addition of Oracle Parallel Servers that cannot be added with the Navigator Service Discovery	Has a pre-7.3.3 Oracle Intelligent Agent

   

Note:  The intelligent agent must be up at discovery time.

    

Important:  If you have upgraded from a pre-8.0.4.1 Oracle Intelligent Agent, you must delete services already discovered and rediscovered them. The 8.0.4.1 and later agents support global database names.

   

To discover services:

1. Login to the Oracle Enterprise Manager Console.

If this in a new install, the discovery wizard will appear.


If this is not a new install, start the wizard. From the Main menu, select Navigator->Service Discovery->Discover New Services, and click the Next button.

2. In the Add Nodes Page, you can enter nodes one-by-one or load them from a text file.

To enter nodes in the wizard, type the node name into the "New Node" field and click the Add button. Repeat for each node.


If you have many nodes, you may want to construct two text files containing their names. The file should contain each node name on its own line. Name the text file *.text so that Oracle Enterprise Manager may find it.

3. Click the Next button.
4. Click the Finish button.

When requested through the Navigator Discovery menu option, the agent passes information from the services.ora file to the Enterprise Manager Console to populate the Navigator tree.

If you could not discover the database(s) in question, please refer to your platform-specific agent. For NT users, please refer to Troubleshooting the NT Agent If It Did Not Start Up on page 1-8. For UNIX users, please refer to Troubleshooting the UNIX Agent If It Did Not Start Up on page 1-16.
 

Note:  Oracle Enterprise Manager no longer uses topology.ora. We recommend that you remove all of the services in the Navigator tree and delete the topology.ora file that was used by the previous release.

   

Since Oracle Enterprise Manager (beginning with version 1.4.0) no longer uses a topology.ora file for Pre-7.3.3 agents, the databases which do not have a 7.3.3 or higher agent running must be manually added to the navigator.

1. Log on to the Oracle Enterprise Manager Console.
2. From the main menu, select: Navigator->Service Discovery->Manually Define Services, and click the Next button.
3. Click on the box "This node contains a Pre-7.3.3 Oracle Intelligent Agent".
4. Enter the Node Name in the "Node Name" box and click the Add button.
5. Under Databases: Enter the database service descriptor defined in the TNSNAMES.ORA file on local box and on the server. The entries should match on both systems.
6. Click the Next button.
7. Click the Finish button.

Enterprise Manager Console and Oracle Names

Oracle Enterprise Manager Console and database applications can resolve service names via Oracle Names like any other Oracle Console application.

1. A client first looks in its own client-side cache. If it has contacted a Names Server within the past 24 hours, the address of a Names Server may be in the cache.
2. If a client has a SQLNET.ORA file, it looks for the NAMES.PREFERRED_SERVER parameter. If one exists, it queries the first Names Server listed.
3. A client looks for a Names Server with a well-known address. The well-known Names Server address on a TCP/IP network is a host aliased to oranamesrvr(), oranamesrvr1,...oranamesrvr4, using port 1575.

For more information on how to configure a client with Oracle Names, see the Oracle Names Administrator's Guide.
 

Note:  Before attempting to discover these services or to run jobs, please test the Net8 connectivity. Please refer to Testing the Connectivity to Any SID on page C-4.

   

Starting Enterprise Manager DBA Applications

You can start an Enterprise Manager database administration application using one of the following methods:

If you are using...	Then...
Console	You can choose from the following three methods:  Select the database you want to administer in the Navigator tree or in the Map window, then choose the application in the Console Tools menu or in the launch palette.  Select the database you want to administer in the Navigator tree, then choose the application from the Related Tools menu of the context-sensitive menu.  Choose the application in the Console Tools menu or in the launch palette, then enter connect information in the Login Information dialog box.
Independent Application	Start the Enterprise Manager Console from the Start menu.  Double-click on the application icon in the Enterprise Manager program group.  Enter the connect information in the Login Information dialog box.
Administration Toolbar	Click on the tool's icon in the toolbar. The tool connects to the default database for the toolbar, if one has been specified.  For information on connecting to other databases, see the online help for the Administration Toolbar.

   

Note:  You can start the database administration applications without running the console. The only exceptions are Backup Manager and Data Manager which use the job system.

   

When a tool executes, it attempts to connect to an Oracle database. For information on connecting to an Oracle database, see the online help.

Before starting an application, when you select a database in the Console, you are connected to the database according to the preferred credentials that have been set up for the database or the credentials you used to log on to the Console. If connection to the database fails for any reason, the Login Information dialog box displays.

Setting Preferences

In order for the agent to execute jobs on a managed node, you must specify valid credentials in the Console.
 

Note:  Jobs will be submitted using the repository owner login account unless the user sets the preferred credentials for the specific service (database, node, listener).

   

To set the preferred credentials, perform the following steps:

1. In the Oracle Enterprise Manager console, select File/Preferences for the services on the machine where the Intelligent Agent is installed
2. Specify the user account that you created as the user preference for the node where the agent is installed by highlighting that node name and entering the account name and password.

For NT users, you must set the preferred credentials for the node (where the NT Agent resides) to be the same as the user that is set up to "Logon as a batch job." The Agent authenticates the user name and password for all owners of jobs that it runs. If you have not set the preferences correctly, the "Failed to authenticate user" error occurs when you submit a job.

For UNIX users, you must specify a valid UNIX operating system user for the node (not db user for database). The user must have operating system privileges to run programs like sqlplus, import/export on the UNIX server. The privilege can be assigned to an existing local or domain user. The "Failed to authenticate user" error will occur if the preferred credentials do not match the account which started the agent.

Configuring a Remote Database for Backup or SYSDBA Administration

Before running the backup subsystem or submitting an administration task, such as database shutdown or startup, through the Oracle Enterprise Manager Job system, you need to set up your database for remote operation.

The following procedure outlines the operations you need to perform on both the server and client. The examples used in the following procedure are for a UNIX environment. Windows NT directories, system variables, and conventions will differ.

Additional Information:

Refer to the operating system-specific documentation for your Oracle database for the exact name of the password file creation utility for your system.

Server Side (UNIX):

1. Login as ORACLE and set your environment variables.

setenv ORACLE_HOME your_oracle_home
setenv ORACLE_SID your_oracle_sid

 

Note:  This example assumes that you have set up your database as ORACLE.

   

2. Change to the dbs directory in your Oracle home.

cd $ORACLE_HOME/dbs

3. Run the ORAPWD executable to create a new password file.

$ORACLE_HOME/bin/orapwd file=orapw<SID> password=your_password entries=10




The file name has to be orapw<SID>. Entries = 10 is the maximum number of distinct DBAs and OPERs.


There should be an orapw<SID> created in $ORACLE_HOME/dbs

4. Edit the init<SID>.ora file. Add or change the following statement remote_login_passwordfile=exclusive in the init<SID>.ora file.
5. Shut down your database and then restart it.
6. Start Server Manager line mode.
7. Connect as sys/sys_password
8. Create a user that will have remote SYSDBA privileges if you do not already have one. In the following example remote is the user name which will have SYSDBA privilege.

create user remote identified by remote;

9. Grant connect and SYSDBA privileges to the user.

grant connect, resource to remote;
grant sysdba to remote;

10. Exit Server Manager Line Mode.

Client Side (Windows NT):

If you want to be able to start up and shut down your target database remotely, follow the steps below:

1. From the Oracle Enterprise Manager Console, select the target database from the Navigator.
2. Start Instance Manager.
3. Log in as a user with the SYSDBA privilege.
4. Double-click Initialization Parameters. The Initialization Parameters Property Sheet appears.
5. Click Save. The Save Configuration property sheet appears.
6. Enter a configuration name.
7. Enter any comments you wish to appear in the Comments column of the Stored Parameters mulit-column list.
8. Click OK.
9. Test the remote SYSDBA login. Start Instance Manager and log in as the user you just created with the SYSDBA privilege. You should be able to startup/shutdown the database using the stored configuration you have created.

Setting Up Backup Modes

If you want to be able to perform on-line backups (hot backups), you must put the database in ARCHIVELOG mode. Otherwise, you must shut down your database; then, perform the backup. By default, the database is in NOARCHIVELOG mode.

To put the database in ARCHIVELOG mode:

1. Edit the following section of the init.ora database initialization file according to its instruction:.

# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true      
# log_archive_dest = %ORACLE_HOME%\database\archive
# log_archive_format = "%%ORACLE_SID%%T%TS%S.ARC"

2. Choose Archive Log from the Database menu. Toggle ARCHIVELOG mode on.

For more information on backup and recover strategies, see the Oracle8 Backup and Recovery Guide.

Recovery Catalog Setup and Registration for Oracle8

The recovery catalog is a repository of information that is used and maintained by Recovery Manager. Recovery Manager uses the information in the recovery catalog to determine how to execute requested backup and restore actions.

To use Oracle8 Recovery Manager with a recovery catalog, you must first install the recovery catalog and then register your database. No setup is required if you are using the control file. It is recommended that you install the recovery catalog on a different location than the target database.

For more information on recovery catalog maintenance, Recovery Manager, and backup and recover strategies, see the Oracle8 Backup and Recovery Guide.

Important:

Your Oracle Enterprise Manager Job system must be functioning properly before attempting to install the recovery catalog. You will need the Job system to register the target database in the recovery catalog.

Setting Up the Recovery Catalog

To set up a recovery catalog, you must complete the following procedures:

• Create a Tablespace
• Create a User
• Run the catrman Script

Create a Tablespace

1. Start Storage Manager.
2. Log in as a user with the DBA role.
3. Select Create from the Tablespace menu. The Create Tablespace property sheet appears.

 

Note:  You can also use the Navigator menu from the Oracle Enterprise Manager console to bring up the Create Tablespace property sheet.

   
4. In the Name field, type the name of the new tablespace. For example, rcvcat.
5. Click the Add button in the Datafiles section. The Create Datafile property sheet appears, allowing you to specify a new datafile which will belong to the new tablespace.
6. In the Name field, type in complete path and name of the datafile. For example: c:\orant\database\rcvcat01.dbf.
7. In the Size section, enter the size of the new datafile. For example, 10 M.
8. Click the OK button in the Create Datafile property sheet.
9. Click the Create button in the Create Tablespace property sheet.

Create a User

1. Start Security Manager.
2. Log in as a user with the DBA role.
3. Choose Create from the User menu. The Create User property sheet appears.

 

Note:  You can also use the Navigator menu from the Oracle Enterprise Manager console to bring up the Create User property sheet.

   
4. In the General Page, fill in the following information:

In the Name field, enter the name of the new user. For example, rman.


In the Password and Confirm Password fields, enter a password. For example, rman.


Choose the default tablespace. For example, RCVCAT.


Choose the temporary tablespace. For example, TEMPORARY_DATA.

5. In the Roles/Privileges Page, fill in the following information:

Choose Role as the Privilege Type.


Grant the RECOVERY_CATALOG_OWNER role to the user.

6. In the Quotas Page, specify an unlimited quota for the default tablespace. In this example, the default tablespace is RCVCAT.
7. Click the Create button after specifying the requisite parameters.

Run the catrman Script

1. Start SQL Worksheet.
2. Enter the requisite login information. For example, user=RMAN, password=RMAN.
3. Execute spool create_rman.log so that errors will be written in a log file.
4. Execute catrman script located in the Oracle_Home/rdbms/admin directory.

Registering the Recovery Catalog with Oracle8 Recovery Manager (GUI)

1. Start the Oracle Enterprise Manager Console.
2. From the File menu, choose Preferences. The User Preferences dialog box appears.
3. Make sure the preferred credentials specify SYSDBA access to any target database that needs to be backed up. Normally, the usernames would be those you created in the previous section. Refer to Setting Up the Recovery Catalog on page 2-16.
4. Select a target database (version 8.0) from the Navigator.
5. Start Oracle Backup Manager. The Backup Subsystem Selection dialog appears.
6. Select Oracle8 Recovery Manager, then click OK. Backup Manager (using the Oracle8 Recovery Manager subsystem) displays.
7. From the Catalog menu, select Use Recovery Catalog.
8. Enter the requisite login information: username, password, and service. For example, user=RMAN, password=RMAN (or any user you create to access the database with the recovery catalog).
9. You are asked if you wish to register the target database in the recovery catalog. Click Register. At this point, the database registration is sent as a job to the Oracle Enterprise Manager Job system.
10. In Backup Manager, click the registration job in the Active Jobs list to see the current state of the job.
11. Once the job is completed, check the job history in the Jobs property sheet to make sure that the job completed successfully.

When the job completes successfully, your backup and recovery environment is configured. For more information on recovery catalog maintenance, Recovery Manager, and backup and recover strategies, see the Oracle8 Backup and Recovery Guide.

Encoding Japanese Characters When Sending Email

A registry key is available for enabling the encoding of Japanese characters when you are sending email.

To set the registry key

1. Run regedit (the Registry Editor).
2. Find the registry key, szDestCharSet, which is located in SOFTWARE\ORACLE\OracleSMPConsole\Email.
3. Double-click the default icon to set the value for szDestCharSet.

Troubleshooting

Please refer to the troubleshooting section below if you should experience any problems during the setup of Oracle Enterprise Manager.

Failed to Authenticate User

"Failed to authenticate user" error occurs when the user submits a job. Use the following hints listed below:

Hint A:

If the agent is on a UNIX platform, check $ORACLE_HOME/bin/dbsnmp and make sure that the dbsnmp executable is owned by root. Refer to Verifying that root.sh Had Been Run Successfully on page 1-11.

Hint B:

For an NT node, make sure the preferred credentials for the node is set to be the same as the user that is set up to "Logon as a batch job." Refer to Setting Preferences on page 2-12.

Hint C:

If an NT agent is started with account other than system, all jobs fail with the message "Failed to authenticate user." This occurs, regardless of whether the job credential account has the "Logon as a batch job" privilege.

Using NT's User Manager from the Administrative Tools program group, you must assign the following privileges (User rights) to the account used to start the agent:

• Log on as service.
• Act as part of the operating system.
• Replace a process level token.
• Increase quotas.

These privileges are required since the NT agent uses CreateProcessAsUser() Win32 API to run jobs. Either create a new account with these privileges or add these privileges to an existing account.

For an example of how to create a new Windows NT user account on the local NT machine and grant privileges to the user, refer to Creating a New NT User Account on page 1-4.

For an example of how to assign privileges to an existing local user account, refer to Assigning Privileges to an Existing NT User Account on page 1-5.

To start the agent on Windows NT as a non-system account, perform the following steps:

1. Double-click the Services icon in the Control Panel folder.
2. Select the OracleAgent service.
1. The Startup Type is set to Manual, which allows the agent to be started by a user. If you want the agent to start automatically whenever you start the system, set the Startup Type for Automatic.
2. Under Log On As section, choose This account (either a local account or domain account).
3. Click the Start push-button to start the agent.

Output from Job Lost

Job fails and the job output window shows:

output from job # lost

Use the following hints listed below:

• If the agent is on a UNIX platform, the preferred credentials are for a user that has write permissions to the $ORACLE_HOME/network/agent directory.
• The catsnmp.sql script has not been run on the database. If the agent is running against an NT database, the catsnmp.sql is run when you install the database and choose to create a starter database. Any other databases you create yourself will not run this script automatically. Please refer to Roles and Users Required by the Agent on page 1-23
• If the agent is running on NT 3.51, the problem has been seen on machines which did not have SP5 installed. Please visit the Microsoft website listed in the readme for information on Service Pack 5.

A job hangs in a "scheduled" state.

Hint A:

On NT, the account must have "Logon as a batch job."

If the Oracle partition is formatted as NTFS (NT File System which allows for local security of files and directories) then you should also grant locally the permission set "Full Control" to the user assigned "Logon as a batch job."

To grant the local file permissions:

1. Click Start, Programs, and Windows NT Explorer.
2. Highlight the drive where Oracle is installed and right click.
3. Select Properties-> Security-> Permissions-> Add-> Show Users.
4. Highlight the account which has been granted "Logon as a batch job" and click Add.
5. Click "Type of Access" and select "Full Control" from the drop down list.
6. Then click OK and OK to close the screen.

Hint B:

Check to see if the agent can access the Console.

Try pinging the Console from the server machine. If you are not sure about your IP address, please check by running the start button-> settings-> control panel-> network-> protocol-> TCP/IP and clicking the properties button.

If you cannot ping the Console, configure the Daemon Manager host address to the TCP/IP address.

Hint C:

Ensure that the DNS Host entry is set to the node name in the listener.ora and tnsnames.ora files.

1. Run the start button-> settings-> control panel-> network-> protocol-> TCP/IP properties.
2. Check the DNS Host entry. For example, make sure that the entry is not set to the name of the previous engineer.

Job Process Crashes

The user running jobs must have read/write permissions to the $ORACLE_HOME\net80 directory (not just $ORACLE_HOME\net80\agent directory) in order to write *.log files as well as write permissions to the $TEMP directory or the $ORACLE_HOME directory.

---