RES: Default database passwords

Patty,
I do not agree with the opinion given that one HAS TO change the password
back to the original.
OW only connects with the actual table owner when it needs to CREATE tables
(otherwise it connects with the system user). That normaly would not be the
case for ESUs, and if, then only for the Business Data of the environment
you are applying the ESU for.
I always like to change ALL table owner's passwords and never had trouble
because of that when applying ESUs.
Here's what you can do:
- If Security is turned OFF on the DS log into JDEPLAN with JDE and whatever
JDE's password is in your Oracle Database.
- If Security is turned ON on the DS create an entry in F98OWSEC (using the
User Security program) for your user (or for JDE) and for each datasource,
using as system user the actual table owner of that datasource and the
respective password. (Probably you will need this only for the Business Data
datasources.)

Let me know if it works for you.
Thanks, Gerd


-----Mensagem original-----
De: [email protected] [mailto[email protected]]Em nome
de SULLY1
Enviada em: sexta-feira, 4 de outubro de 2002 15:20
Para: [email protected]
Assunto: Re: Default database passwords


Thanks for the response. What about the oracle JDE user and the OneWorld
JDE user?

Patty
XE/SP18.1/One-off SP.18_E1/U5 Unix HP900, Oracle 8.1.6
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=42993
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+


********Confidencialidade do Correio do Eletrônico

In the earlier versions of OW, the jde password had to be the default, but that requirement has been removed now.

So, you need to have PRODDTA and other table owners in the F98OWSEC in order to change their passwords on the database as well as in F98OWSEC? If you are running Security Server...

I tried this fix recently but it still had problems in R98403 copying one environments business data to a second environment. One thing that did surprise me from the logs was that it appeared to be doing a GRANT to PUBLIC in the process which failed. I can see no good reason for it to do this at all and it sounds very dodgy!

To get the job done I temporarily reset the xxxDTA user passwords back to their defaults at the ORACLE level, ran the UBE and changed them back. I guess you could call it security.

OneWorld really sets Oracle object privs to public everytime the table is created. Someone has to run scripts to revoke privs from public (except indexing and another, which must stay public) and set to a role that the database user and datasource owner is using.