R98403 and table owners...

[swhitmire]

It's been mentioned here before that R98403 assumes the passwords for the
table owners are
the same as the owner names and that SARs have been entered about this...
can anyone
point me to a SAR number? Also, are there any other processes known to
suffer from this
problem?

--Scotti Whitmire
DeRoyal Industries
Xe Upd2, SP17.1, AIX4.3.3, Oracle 8.1.6

 

[cdawes8]

Yes, by default the R98403 assumes that the password for the table owners
are the same as the owner name. If not you will be prompted for the table
owner password for every single table copy. However, if you don't change the
password on the table owners anyone with SQL Plus can have a very happy time
with your data. One way to get around this while still changing the
passwords is for the JDE user set up System security in P98OWSEC for each
JDE datasource (each Oracle owner). ie. add a datasource for Business Data -
PROD, Control Tables - PROD, Central Objects - PROD, etc. This way JDE will
simply use the password that you specify here and won't prompt you or try
and use the default password on each table space that everyone knows.

Colin


Colin Dawes
City of Guelph (somewhere near Toronto, somewhere in Canada)
B733.2 SP17.1_B1, Intel/NT/Oracle 8.1.7.1 FAT & TSE

 

[Larry_Jones]

Hi Scotti,

I appreciate the difficulties in finding these SARs. Recently JDE seems to have changed the search mechanism and not for the better - I really have to get imaginative in some of my searches now.

Anyway - SARs.
4572727 - R98403 and database passwords. Target release is B9.
4408986 - R98403 Failes w/Password change. (Old SAR)

There are several other, older SARs on this issue. JDE apparently decided to avoid the issue until B9. 4572727 is completed so apparently the fix is in for B9 - leaving us still stranded for now.

If you're worried about the effects of changing owner passwords - don't be. As far as I know the only time these are needed are:
1) When running R98403
2) Generating a table or index in OMW (I believe you're prompted then)
3) When upgrading or installing (i.e. installing XE). Potentially an update may also need this changed - if a table needs to be created or modified - so read install instructions closely as always.

We run with the passwords changed from their default values and only temporarily change back when forced to by the above conditions. Its still a security hole - all we can do is limit how long the hole is open.

Regards,



Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials

 

[mtrottier]

There a couple SARs for this but the latest one is # 4572727. It will also be an issue when using the following:

Table and Index Creation B98407
Environment Database Creation R98403
Create Planner Tables B9800403
Installation Workbench P9841
Installation Planner Director P98410
Environment Workbench P98411
Launch Table Conversion B984054

You can work around the issue with Table and Index Creation because you can override the password.

The remaining ones can be a big issue during Upgrades, Updates and potentially during some ASU/ESU’s.

For one client I recently implemented a process using SQL scripts where they can easily switch the passwords back and forth across all their Oracle instances as needed.

Mike


Mike Trottier
Independent CNC Consultant
Onsite and Dial-up Support
B731,B732,B733,XE
AS400,Unix,NT
Oracle,SQL
#801 557-8368