Libname issues on 9.4

[danielmitu]

Hello,

I have a job and the output is a oracle table/library.

The user should not have access to modify this Oracle table.

The user is part of an Access Control Template that has only RM.

I compare another library and I found that in the first one, when I click on Libname I see this:

LIBNAME xxxxxx ORACLE  ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=NO DBCLIENT_MAX_BYTES=1 DBSERVER_MAX_BYTES=1  PATH=XXXXXX.WORLD  SCHEMA=YYYYY  USER=AAAAAA  PASSWORD="{SAS002}cxcxxsdasdsa" ;

In the second libname I see this:

LIBNAME xxxxxxx ORACLE  DBMAX_TEXT=4000  PATH=XXXXXX  SCHEMA=aaaaaaaaa  AUTHDOMAIN="aaaaaaa" ;

How can I set the libname for the first library like the second one. TO have only the AUTHDOMAIN, not the user and password saved.

Thanks

[LinusH]

Are both generated from meta data?
If so, "just" comapre all settings for the library (and connected schema and database objects).

[danielmitu]

Hello,

I don't understand the question.

Can you explain?

Thank

[Patrick]

@danielmitu

Both libname syntax you've posted will give the user who is executing the code access to Oracle.

The libname code gets generated based on the library metadata definition and though if you want to figure out what to change in metadata for the first library simply compare it with the metadata definition for the 2nd library.