Alter SYS & SYSTEM pwd on any database

I have 96 instances and have to establish a policy of enforced SYS & SYSTEM password changes on a monthly basis.
I would like to schedule an OEM job to do it; does anyone have any experience of doing this? I believe it can be done as a PL/SQL job using the DBMS_SQL.OPEN_CURSOR and DBMS_SQL.PARSE procedures to execute the alter user command.
Any help gratefully received.

96 instances? do you have to administer the same users on all databases as well? If so, you might want to go for an account sync-ing solution where all credentials are stored in a central place and a change of a user in any of the databases or the central place will update all 96 instances for you. Novell's DirXml will do just that for you. I've had some great experiences with it.
(I don't have much experience with jobs, so sorry, no direct answer from me)
L.

Similar Messages

OracleXE Newbie: How do I view user tables as SYS/SYSTEM?

I'm brand new to Oracle and downloade OracleXE to learn a bit about it. When I login as SYS or SYSTEM how do I view user tables? Don't I have full admin rights? I can't figure it out.
I've unlocked the sample application with the user HR and created the first sample app page to view Employees, and when logged in as HR I can see all of the tables but why not when I'm signed in as SYS or SYSTEM?
TIA

The sys and system users can see (and alter, drop, create) objects for any database user, just have to add the schema (a.k.a. database username) to the object name, i.e.
select * from hr.employees;
Should get you the hr employees table. There are also several views to help out, i.e. dba_users has all the database users, dba_objects for all objects in the database objects, dba_tables has all tables, etc.
And each user also gets similar views, user_tables has all the tables that user has created, and there is an all_tables view listing any table the user has been granted select or other privileges.

SYS, SYSTEM and SYSAUX when full database refresh.

I took full export from database using below command
expdp "'/ as sysdba'" full=Y directory=DPUMP_DIR dumpfile=expdp_11032011.dmp logfile=expdp_11032011.log Now, I need to import this file to an other database.
When do schema refresh we usually drop all the object in that schema and start refresh, but when doing fullback up, do we need to drop all user?
what about sys, system and sysaux user?

user3636719 wrote:
So, the tables in the SYS and SYSTEM will remain same when we refresh?
Structure will not be modified but contents will be automatically modified when DLL is executed when importing.
And do we have to drop other user before we import?Applications schemas that you have created should be dropped. In general don't modify any schema that is directly managed by Oracle such as SYS or SYSTEM or any schema used by some database option like Oracle Text, Oracle Spatial, etc.

Can Enterprise Java Beans interact with any database system

Hello:
I was wondering if someone can tell me if the Enterprise javabeans can work with any database (like multi-valued database for example Universe)?
Thanks in advance.
Rino

Yes

Sys user pwd Understanding as sysdba

os : linux
oracle : 10.2.0.3
I am able to connect sys as sysdba No problem.
on Server terminal : sys is working with any pwd as sysdba.
SQL> connect sys/gln as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> connect sys/a as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> connect sys/b as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL>
However if we connecting thru tnsnames it is validataing not allowing.
How to understand this.
connect sys/anypwd as sysdba is just nothing connect / as sysdba ?
SQL> connect system/anypwd as sysdba
Connected.
SQL> show user
USER is "SYS"
So sysdba is not a previlege but a role?
pl. clarify.

This fact is know as OS authentication, on a windows system you are connecting at the os level with a user that belongs to the database privileged group ORA_DBA and the windows authentication services is declared at the sqlnet.ora file.
On a unix environment it means your user belongs to the dba (or equivalent) privileged group -declared at install time- so as long as you connect locally you won't be requested to provide a valid password, but if you get connected remotely the only way to know you are a valid administrator is by means of the administrator's password (oracle password file)
~ Madrid

Is X-windows and GUI desktops supported on the ODA "engineered system" running a RAC database? If it is, what is the yum command needed to install the X-windows, Gnome, and KDE package groups?

Is X-windows and GUI desktops supported on the ODA "engineered system" running a RAC database? If it is, what is the yum command needed to install the X-windows, Gnome, and KDE package groups?

While I agree with the direction of the suggestions with installing packages for X-windows, we do not have a blanket 'apply any package' recommendation.
In particular we do not support altering the kernel (although we do have exceptions which we review on a case by case basis).
Basically, if the you want to alter functionality that would not impact core functionality you are usually fine.
A good guideling is : The more dependencies that there are between the package / rpm you are considering using the higher the potential impact on functionality - meaning higher chance for problems
Note: We do use VNC including Real and Tiger regularly , but we have no hard recommendation on how you may want to use X-windows. I have never seen a limitation other than comments on bugs
or incompatibility within the X-window product itself with certain kernel levels.
Patching may overwrite some packages that you may install, however, _depending on packages/rpms added_ there is also the possibility that you will break existing functionality to the point
that patching itself will fail ( we have already seen a few cases of this in which case the proper mitigation is to remove / roll-back any alterations to the ODA before patching, and then adding the packages/rpms
back after the patching is completed.
From what you are discussing the impact should be low without conflicts, but please consider the above, and if you have specific packages which you consider potential problems
please create an SR so that we can review packages / rpms on an individual basis.
Once again: the main criteria for not supporting rpms is regarding the kernel itself
Chuck

ALTER USER를 실행한 사용자를 확인하는 방법(SYSTEM EVENT TRIGGER)

제품 : ORACLE SERVER
작성날짜 : 2002-11-07
ALTER USER를 실행한 사용자를 확인하는 방법(SYSTEM EVENT TRIGGER)
================================================================
PURPOSE
자신이나 또는 다른 user들의 password를 바꾸는 등의 alter user command를
사용한 사용자를 확인하는 방법을 알아보자.
Explanation & Example
1. 사용자 정보를 저장할 event table을 생성한다.
Create event table and users to store the alterations made:
SQL> connect / as sysdba;
create table event_table
ora_sysevent varchar2(20),
ora_login_user varchar2(30),
ora_instance_num number,
ora_database_name varchar2(50),
ora_dict_obj_name varchar2(30),
ora_dict_obj_type varchar2(20),
ora_dict_obj_owner varchar2(30),
timestamp date
create user test1 identified by test1;
grant create session, alter user to test1;
create user test2 identified by test2;
grant create session to test2;
2. SYS user에서 AFTER ALTER Client Event Trigger 를 생성한다.
Note: This step creates a trigger and it is fired whenever the user "test1"
issues ALTER command (It can be ALTER USER or ALTER TABLE)
SQL> CREATE or REPLACE TRIGGER after_alter AFTER ALTER on database
BEGIN
IF (ora_dict_obj_type='USER') THEN
insert into event_table
values (ora_sysevent,
ora_login_user,
ora_instance_num,
ora_database_name,
ora_dict_obj_name,
ora_dict_obj_type,
ora_dict_obj_owner,
sysdate);
END IF;
END;
3. test1 user로 접속한 후 test2 user의 password를 변경하는 작업을 실행한다.
SQL> connect test1/test1
SQL> alter user test2 identified by foo;
4. test2 user의 password가 test1 user에 의해 변경되면 그런 내용을
event_table 에서 확인할 수 있다.
Now that we have altered the "test2" user password from user "test1", the
event_table should have captured this details.
Now Login in as sys and Query on event_table:
SQL> connect / as sysdba;
SQL> select * from event_table;
ORA_SYSEVENT ORA_LOGIN_USER ORA_INSTANCE_NUM
ORA_DATABASE_NAME
ORA_DICT_OBJ_NAME ORA_DICT_OBJ_TYPE
ORA_DICT_OBJ_OWNER TIMESTAMP
ALTER TEST1 1
T901.IDC.ORACLE.COM
TEST2 USER
13-JUN-02
event_table의 내용을 조회하여 LOGIN_USER와 ALTERED USER 는
ORA_LOGIN_USER와 ORA_DICT_OBJ_NAME column을 통해 확인할 수 있다.
비슷한 방법으로 아래의 event에서 trigger를 생성하여 확인할 수 있다.
1) BEFORE DROP
2) AFTER DROP
3) BEFORE ANALYZE
4) AFTER ANALYZE
5) BEFORE DDL
6) AFTER DDL
7) BEFORE TRUNCATE
8) AFTER TRUNCATE
Related Documents
Oracle Application Developer's Guide

Oracle SYS/SYSTEM shared passwords

Unfortunately we have a requirement not to have the sys/system passwords shared even among the DBA staff. Someone mentioned an Oracle article which details not having shared passwords. The problem is that security perceives this issue as a threat. I have argued until I am blue in the face that these two accounts are needed by the dba team. Does anyone have any information on this subject to pass along? Things that worked and even those that didnt? The real issue comes into play when you start looking at cron jobs on the oracle account which have most of the privileged passwords visible.
Thanks!

You could argue that with me - a DBA - until you are blue in the face and you would still loose. You DO NOT need the sys and system accounts to do your job as a DBA.
Here is what we do...
1. create a role, or set of roles something like DBA_SENIOR, DBA_SECURITY, DBA_USERADMIN, etc. Give them all of the privileges they need for their specific jobs.
2. create user accounts for each DBA - we use externally identified but they need not be.
3. grant each DBA his appropriate role.
4. create a password file.
5. grant sysdba to the DBAs - so that they can become SYS on those times when it is the only way to do what needs to be done.
6. give sys and system impossible passwords.
7. DO NOT grant DBA role to anyone.
Now you have met the requirement and your dba's can do their jobs. And if you create scripts, then it is easy to make this routine for whenever you create a database.

Sys log trigger in cluster database

Hi Experts,
We have 3 nodes cluster database. How do we create a sys log trigger in cluster database?
Do I need to create a system log trigger at each database instance in 3 node(instance) cluster database? or only create one system log trigger in one instance?
Thanks
Jin

A RAC database is a single database with many instances: one database means one logon trigger.
You just need to create the logon trigger when connected to any instance of the same database.

Setting password limits on SYS, SYSTEM, DBSNMP

We are having a security audit conducted and the auditors want us to set password limits for system accounts (SYS, SYSTEM, DBSNMP). They're asking us to set PASSWORD_LIFE_TIME, PASSWORD_GRACE_TIME, PASSWORD_REUSE_MAX, PASSWORD_REUSE_TIME. I have not been able to find any documentation that discusses the implications of doing this, if any. I'm wondering what will happen if these accounts become locked and/or expired because of invalid login attempts and not changing the password in time. I need something definitive one way or the other to show the customer. Please help!
Thanks,
Susan

Which operating System and which database release?
In AIX you can define password limit on OS level (using smitty for it) very straight forward.
You can also use OEM to do the password configuration which includes your assignment.
DN

Shrink system tablespace, or any laternate to reduce disk space usage!

Dear All,
My Database is 11gR1 and Linux is the operating system.
My System tablespace is consuming 24,000 MB disk space, The user i have created that contain all the objects is another tablespace.
I just want to know is there any way to shrink system tablespace or anything else that can be done to reduce its size?
Plus what are the directories from where we can delete logs and other files that do not affect the running of database. My disk space is 99% full and i have to delete files.
Regards, Imran

misterimran wrote:
Dear All,
My Database is 11gR1 and Linux is the operating system.
My System tablespace is consuming 24,000 MB disk space, The user i have created that contain all the objects is another tablespace.
I just want to know is there any way to shrink system tablespace or anything else that can be done to reduce its size?
Plus what are the directories from where we can delete logs and other files that do not affect the running of database. My disk space is 99% full and i have to delete files.
Regards, ImranFirst, do this:
sql> select distinct owner from dba_segments where tablespace_name = 'SYSTEM';Make sure the only objects in the SYSTEM ts are owned by legit users of that ts - SYS, SYSTEM, and OUTLN
As for log files .. look at your listener log. look at your alert log. look at any trace files in adump, bdump and udump that are old enough you don't want them any more.

What is the Relation between SAP EP, SAP R/3 and any database

Hi ALL,
I am learning SAP EP,Webdynpro
Previously I have worked on IBM WebSphere Portal for installation and configuration test purpose on different operating systems.
In case of IBM webSphere Portal
1. There is a default database named as Cloudspace
2. I had configured WebSphere Portal with different databases(Oracle,sql,DB2) just by modifing some portal installation files.
Similarly in case of SAP Enterprise Portal
1. Is there any default database.
2. How can we configure the portal with different databases(Oracle,sql,DB2)
3. Why the SAP R/3 comes into the picture in case of SAP EP
4. can we communicate to any database(Oracle,sql,DB2) through NetWeaver Developer Studio by writing any code or by setting any fields.
Please help out me
Regards
Seshu

Hi! Sesshanna,
   Welcome to SAP Enterprise Portal.
1.Like IBM webSphere Portal,SAP EP is also have a default DataBase Named MaxDB, this database comes with portal installer and you need to install this DataBase as well.
2.you will get a lots of document on SDN to configure the databases like(Oracle,sql,DB2), you need to make an entry in Visual Administrator(go.bat).But if you want to use DataBase in standalone application then you can use the same code which generally we use in any Java Code(Code written in point 4).
3.You can use SAP R/3 as BackEnd to access R/3 RFC in WebDynpro application, which is used to develop any customized application.
4.you can write the following code in any view or controller of the NWDS:--
MessageManager msgMgr = (MessageManager)wdThis.wdGetAPI().
getComponent().getMessageManager();
                String serverName = "172.21.1.62";
     String portNumber = "1526";
     String sid = "vision";
String url = "jdbc:oracle:thin:@" + serverName + ":" + portNumber + ":" + sid;
     String userName = "scott";
     String password = "tiger";
     Connection connection = null;
     try {
      // Load the JDBC driver
     String driverName = "oracle.jdbc.driver.OracleDriver";
     Class.forName(driverName);
     connection = DriverManager.getConnection(url, userName, password);
     Statement stmt =connection.createStatement();
ResultSet resultSet = stmt.executeQuery("select * from patni_employee");
        if(resultSet.next()) {
          msgMgr.reportWarning(resultSet.getString(1));
          msgMgr.reportWarning(resultSet.getString(2));
     } catch(Exception exc) {
      exc.printStackTrace();
regards,
Mithileshwar

Can Visual Composer talk to/connect to any database?..

Hi ,
My first question is if Visual Composer can talk to a database directly?
I would like to know the all the databases which visual composer can connect to?
Does it connect only to SAP Backend systems?
Or can it connect to Any Database like SQL server etc.,?
If so, how can visual composer be configured to any database?...
Please help!
Thanks,
Vaishali.

Hi Vaishali,
It can talk to Any SAP Data base or Java or Oracle data base through portal.
First you have to confihure all your backends in Your portal and Connect them to Your VC User through Usermapping.
So all Backends will appear in VC There by you can use the for your application in your portal.
If helpful award points
Regards,
Govindu

RMAN Backup job fails after changing sys, system passwords

Hello Oracle community,
11.1g
After we changed the passwords for sys, system and sysman the backup jobs fails. this is my error log:
Recovery Manager: Release 11.1.0.7.0 - Production on Mo Aug 30 11:16:29 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12532: TNS: Ungültiges Argument
RMAN>
Echo einstellen ein
RMAN> set command id to 'BACKUP_MEGALON.INT_083010111617';
Befehl wird ausgeführt: SET COMMAND ID
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei set Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' database;
Starten backup um 30.08.10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' archivelog all not backed up;
Starten backup um 30.08.10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> exit;
Recovery Manager abgeschlossen.
Ikrischer

Hello Tychos,
I am able to make a sqlplus connection, but your hint send me in the correct direction. I had a special character "@" in the password and I think that was the reason for my problems with RMAN.
Ikrischer

Alter user system identified by manager; need help

SQL> connect /as sysdba;
Connected.
SQL> alter user system account unlock;
User altered.
SQL> alter user system identified by manager;
User altered.
SQL> connect system/manager@q17als;
ERROR:
ORA-28000: the account is locked
Warning: You are no longer connected to ORACLE.

can you try do to the connect system/manager without
putting the @q17als on it?
I bet it will work
Well that one should work, although it may not connect to the right database.
What may have happened is he logged in to a different database using "/as sysdba" and unlocked SYSTEM account there. Therefore connecting as system without using an alias would work (if the password is manager).
the net service name for q17als probably uses different database in its connect descriptor. We can see that if we know what connect descriptor for q17als looks like. (tnsping q17als or checking tnsnames.ora)
I agree with the earlier posts - I think you are
dealing with two different databasesThat is what I am trying to prove as well

Alter SYS & SYSTEM pwd on any database

Similar Messages

Maybe you are looking for