Re: [suse-oracle] Auth errors submitting jobs on 7.2 with DB 8.1.7 and OEM 2.2

Philippe_De_Mild@wet.recticel.be
Date: Tue Oct 23 2001 - 07:01:05 PDT

Next message: Eric.Desai@ebancllc.com: "[suse-oracle] lsnrctl dbsnmp_start does not exist for 9i"

Previous message: Jason Lantz: "Re: [suse-oracle] Off topic - just a bit - Suse vs Redhat"
Maybe in reply to: Philippe_De_Mild@wet.recticel.be: "[suse-oracle] Auth errors submitting jobs on 7.2 with DB 8.1.7 and OEM 2.2"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Message-ID: <OFE0FEBF3B.E1CCFC83-ONC1256AEE.004CF9E8@recticel.com>
From: Philippe_De_Mild@wet.recticel.be
Date: Tue, 23 Oct 2001 16:01:05 +0200
Subject: Re: [suse-oracle] Auth errors submitting jobs on 7.2 with DB 8.1.7 and OEM 2.2

Hi,
Sorry to bother, managed to get around this one.
Must have screwed up sth on the first machine, because it worked out of the
box on the second.
Anyway (-rwxr-xr-x oracle oinstall dbsnmp) is OK if you only want
oracle jobs to run.

Bye
Philippe

                    Philippe_De_Mild@wet.r
                    ecticel.be To: suse-oracle@suse.com
                                                  cc:
                    22/10/2001 14:10 Subject: [suse-oracle] Auth errors submitting jobs on 7.2 with DB
                                                  8.1.7 and OEM 2.2

Hi,
I was wondering if anyone out there also uses OEM 2.2 against Oracle 8.1.7
db's on SuSE 7.2.
The issue is that I am unable to run jobs ( OS as well as database, even
though everything else seems to work fine ( OEM tools, discovery, ... ))

I've looked at all the obvious stuff ( credentials, file and directory
authorisations, ... ) and noted that the authorisation set at the dbsnmp
binary is different from what Oracle indicates
Initially they were at
-rwxr-xr-x oracle oinstall dbsnmp
It looks like this is the result of applying the required glibc patch in
order to support 8.1.x databases on 2.4 kernels.

At this point I was getting internal Oracle errors ORA-1017, even though I
was using plain vanilla "system" access to issue an export. The access for
dbsnmp was OK too.

However when I change the setting ( either by re-running root.sh or
manually play with it ) to
-rwsr-xr-x root oinstall dbsnmp or even
-rwsr-s--- root oinstall dbsnmp

I'm getting VNI-2015, regardless of whether it's an OS job or a database
job ( OS credentials are set to Oracle, Database credentials are set to
system )

Must root have any additional setting opened at the OS level? Telnet and
ftp are closed ( shouldn't be an issue, it's all on the same box ). Anyway
oracle has those and I still cannot get stuff to work.

Any ideas highly appreciated

Philippe

BTW I only joined the list a couple of months ago and this may very well be
old news. Am I correct that there are a number of "glitches" in the root.sh
script the way it is written by Oracle during the installation process?? I
am aware of the ' issue ( thank you SuSE ) but what about the /n appearing
and rm -f not behaving?

---------------------------------------------------------------------
To unsubscribe, e-mail: suse-oracle-unsubscribe@suse.com
For additional commands, e-mail: suse-oracle-help@suse.com

Next message: Eric.Desai@ebancllc.com: "[suse-oracle] lsnrctl dbsnmp_start does not exist for 9i"
Previous message: Jason Lantz: "Re: [suse-oracle] Off topic - just a bit - Suse vs Redhat"
Maybe in reply to: Philippe_De_Mild@wet.recticel.be: "[suse-oracle] Auth errors submitting jobs on 7.2 with DB 8.1.7 and OEM 2.2"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.0 : Tue Oct 23 2001 - 07:01:17 PDT