Then your solution doesn't help me.. We were able to create the DB on = AIX with remote password authentication without ODM. Thanks though. -----Original Message----- From: askdba-bounce@xxxxxxxxxxxxx [mailto:askdba-bounce@xxxxxxxxxxxxx] = On Behalf Of Pepling, Todd C. Sent: Friday, December 03, 2004 10:25 AM To: 'askdba@xxxxxxxxxxxxx' Subject: [askdba] Re: Oracle ODM AIX I don't believe 8.0.5 had ODM, thus it's not neither an AIX issue nor an = ODM issue. > -----Original Message----- > From: askdba-bounce@xxxxxxxxxxxxx > [mailto:askdba-bounce@xxxxxxxxxxxxx]On > Behalf Of Patricia Eyenga > Sent: Friday, December 03, 2004 10:00 AM > To: askdba@xxxxxxxxxxxxx > Subject: [askdba] Re: Oracle ODM AIX >=20 >=20 > I'm just wondering if it's an ODM issue or an AIX issue. I > suppose I =3D > could > do as you suggest, but would also like to know it this is=20 > ODM-related or =3D > not >=20 > -----Original Message----- > From: askdba-bounce@xxxxxxxxxxxxx > [mailto:askdba-bounce@xxxxxxxxxxxxx] =3D > On > Behalf Of Pepling, Todd C. > Sent: Friday, December 03, 2004 9:06 AM > To: 'askdba@xxxxxxxxxxxxx' > Subject: [askdba] Re: Oracle ODM AIX >=20 >=20 > This was standard for Oracle 8.0.5 on WinNT 4.0. I always > created the =3D > DB > first w/ remote_login_passwordfile=3D3Dnone, then created the password = =3D > file, > then changed remote_login_passwordfile=3D3Dexclusive, then=20 > bounced the DB. >=20 > Is there a reason you can't do this? >=20 > > -----Original Message----- > > From: askdba-bounce@xxxxxxxxxxxxx =20 > >[mailto:askdba-bounce@xxxxxxxxxxxxx]On > > Behalf Of Patricia Eyenga > > Sent: Friday, December 03, 2004 8:58 AM > > To: askdba@xxxxxxxxxxxxx > > Subject: [askdba] Oracle ODM AIX > >=3D20 > >=3D20 > > Is anyone out there using Oracle 9i with ODM (we're on AIX, but I'm = > >not sure this problem would be limited to AIX)... > > =3D20 > > The issue we're having is that setting the > > remote_login_passwordfile to > > anything other than 'NONE' generates the following error when=3D20 > > creating the > > DB: > > ORA-01501: CREATE DATABASE failed > > ORA-00600: internal error code, arguments: [ksfd_odmopn2],=20 > [ODM ERROR > > V-41-4-19 No such device], [], [], [], [], [], [] > > Error 600 happened during db open, shutting down database=3D20 > > USER: terminating instance due to error 600 > > =3D20 > > I also see the following in the trace file:=3D20 > > =3D > ksfdopn:fname=3D3D/u01/ARBPRDDB/app/oracle/product/9205/dbs/orap > wIBMPRDDB0 > > blksiz=3D3D512 ftype=3D3D8 flags=3D3D0x0 ps=3D3D0x0 fno=3D3D0=3D20=20 > > ksfd_odmopn:fname=3D3D/u01/ARBPRDDB/app/oracle/product/9205/dbs/or > > apwIBMPRDDB0 > > blksiz=3D3D512 ftype=3D3D8 flags=3D3D0x0 ps=3D3D0xe43656a0 = fno=3D3D0=3D20=20 > > ksfd_fibd:fib=3D3D0xe3d2abe0 flags=3D3D0x0 > > *** 2004-12-02 22:24:35.511 > > ksedmp: internal or fatal error > > ORA-00600: internal error code, arguments: [ksfd_odmopn2], > [ODM ERROR=3D20 > > V-41-4-19 No such device], [], [], [], [], [], [] > > =3D20 > > =3D20 > > although at the beginning of the create statement the following=20 > > succeeds: =3D > ksfdopn:fname=3D3D/u01/ARBPRDDB/app/oracle/product/9205/dbs/orap > wIBMPRDDB0 > > blksiz=3D3D512 ftype=3D3D8 flags=3D3D0x0 ps=3D3D0x0 fno=3D3D0=3D20 > > ksfdopn: fob=3D3D0xe705d098 fib=3D3D0xe3d29b78=3D20 > >=3D20 > > =3D20 > > Anyone have any clue? > >=3D20 > >=3D20 > >=3D20 > This email and any files transmitted with it are confidential and =3D=20 > intended solely for the use of the individual or entity to whom they=20 > are =3D addressed. > If you have received this email in error please notify the system =3D > manager. > This message contains confidential information and is=20 > intended only for =3D > the > individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. >=20 >=20 >=20 This email and any files transmitted with it are confidential and = intended solely for the use of the individual or entity to whom they are = addressed. If you have received this email in error please notify the system = manager. This message contains confidential information and is intended only for = the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.