Skip Headers
Oracle® Identity Manager Connector Guide for IBM RACF Advanced
Release 9.0.4

Part Number E10451-20
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

F Mainframe Problem Source Identification and Problem Determination

Table F-1 describes Mainframe Problem Source Identification and Problem Determination.

Table F-1 Mainframe Problem Source Identification and Problem Determination

Problem Source Identification Problem Determination

Voyager unable to connect to the LDAP

  1. Can the LDAP server be pinged?

  2. Is the LDAP up?

  3. Is the LDAP listening on the correct port? Must be what is defined on PORT= on Voyager

  4. Can the Server where the LDAP resides Ping Voyager?

Voyager abends: S306-30 or

Pioneer abends: S306-30

Review all RACF definitions. This abend is a incorrect definition.

Voyager or Pioneer abends other than S306-30 and SB37, SD37 or SE37

Open an Oracle SR and send the Voyager/Pioneer STC logs.

LDAP cant connect to Pioneer

  1. Verify the listening port is correct on Pioneer, must be PORT=

  2. Can the LDAP server ping Pioneer?

  3. Can Pioneer ping the Server?

ADDUSER,ALTUSER,ADDGROUP,DELUSER submitted by LDAP and it fails.

Fails with SAF RC=8, RACF RC = 8

Incorrect RACF definitions for Pioneer. Must have access to all irr.radmin.* functions.

No Data in Voyager subpool. No events coming to the LDAP

  1. Verify the three exits are up by:

    "D PROG,EXIT" the command exit should be active, "IRREVX01"

  2. Review syslog for this message:

    ICH508I ACTIVE RACF EXITS: ICHRIX02 ICHPWX01