System User access?

Hi Friends,
We are having some access problem to System user ALEREMOTE in BW system.
We know suitable roles for this problem.
But i would like to know if any precautions (or) points need to be considered before giving more access to the System User?
Please give me your comments.
Thanks
Tony

Hi,
I don't think there is any harm in giving more access to System user because it's a background user and no dailog can abuse the authorizations.
Hope this tip helps.
Cheers
Bala Koppuravuri

Similar Messages

How to 'Remove' user access from deleted dual boot system's users in existing operating system's folders and files?

I have Windows 7 Enterprise Professional, accessed earlier from (now deleted) other dual boot operating system (User folder), which shows it's users as unknowns for folder properties in Windows 7 Enterprise Professional's "C:\Users\Aniruddha",
which causes system not responding, how to 'Remove' these unknown users from folder properties of "C:\Users\Aniruddha"?
Also "C:\Users\Aniruddha\Application Data" creates many of own folders within eachselfs end folder ("C:\Users\Aniruddha\Application Data" creates a "C:\Users\Aniruddha\Application Data\Application Data", "C:\Users\Aniruddha\Application
Data\Application Data" creates a "C:\Users\Aniruddha\Application Data\Application Data\Application Data" and many) because of which system stops responding randomly, starts responding only for "ctrl+alt+del", why such self
creation begins?
Whether a standby user with same file structure copied from a user would dynamically link it's shortcut folders with Windows user from whom these folders were copied or whether there would be no link and for above said problem I would restore User's file structre
back to normal just by copying from standby user?

It seems your PC is infected with some malware. Use a trusted antivirus software with the latest definition updates installed to scan and remove the malware.
Balaji Kundalam

Creating new user having same access as that of SYSTEM user in Express Edit

Hi, is it possible in oracle to create a new user having same access as that of SYSTEM user?
If yes what would be syntax?
If not i would like to create a user having most of admin rights likes exporting and importing schemas and all.
How it can be done?
Any help would be appreciated.. :)
I am using Express Edition 11g.

same access as that of SYSTEM usergrant dba to <username>;
Its not exactly system equivalent, sys does grant a few rights directly to system database user but its pretty darn close.
exporting and importing schemasgrant datapump_exp_full_database to <username>;
grant datapump_imp_full_database to <username>;

Creating new user having same access as that of SYSTEM user.

Hi, is it possible in oracle to create a new user having same access as that of SYSTEM user?
If yes what would be syntax?
If not i would like to create a user having most of admin rights likes exporting and importing schemas and all.
How it can be done?
Any help would be appreciated.. :)

Try the below command here "SYF" is the user wchich will be created that will have system privileges: -
CREATE USER "SYF" PROFILE "DEFAULT" IDENTIFIED BY "*******" DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK
GRANT CREATE MATERIALIZED VIEW TO "SYF"
GRANT CREATE TABLE TO "SYF"
GRANT GLOBAL QUERY REWRITE TO "SYF"
GRANT SELECT ANY TABLE TO "SYF"
GRANT UNLIMITED TABLESPACE TO "SYF" WITH ADMIN OPTION
GRANT EXECUTE ON "SYS"."CHECK_UPGRADE" TO "SYF"
GRANT EXECUTE ON "SYS"."DBMS_ALERT" TO "SYF"
GRANT EXECUTE ON "SYS"."DBMS_AQ" TO "SYF" WITH GRANT OPTION
GRANT EXECUTE ON "SYS"."DBMS_AQADM" TO "SYF" WITH GRANT OPTION
GRANT EXECUTE ON "SYS"."DBMS_AQELM" TO "SYF" WITH GRANT OPTION
GRANT EXECUTE ON "SYS"."DBMS_AQ_IMPORT_INTERNAL" TO "SYF" WITH GRANT OPTION
GRANT EXECUTE ON "SYS"."DBMS_DEFER_IMPORT_INTERNAL" TO "SYF"
GRANT EXECUTE ON "SYS"."DBMS_REPCAT" TO "SYF"
GRANT EXECUTE ON "SYS"."DBMS_RULE_EXIMP" TO "SYF" WITH GRANT OPTION
GRANT EXECUTE ON "SYS"."DBMS_SYS_ERROR" TO "SYF"
GRANT EXECUTE ON "SYS"."DBMS_TRANSFORM_EXIMP" TO "SYF" WITH GRANT OPTION
GRANT READ ON DIRECTORY "SYS"."DPUMP" TO "SYF"
GRANT WRITE ON DIRECTORY "SYS"."DPUMP" TO "SYF"
GRANT ALTER ON "SYS"."INCEXP" TO "SYF"
GRANT DEBUG ON "SYS"."INCEXP" TO "SYF"
GRANT DELETE ON "SYS"."INCEXP" TO "SYF"
GRANT FLASHBACK ON "SYS"."INCEXP" TO "SYF"
GRANT INDEX ON "SYS"."INCEXP" TO "SYF"
GRANT INSERT ON "SYS"."INCEXP" TO "SYF"
GRANT ON COMMIT REFRESH ON "SYS"."INCEXP" TO "SYF"
GRANT QUERY REWRITE ON "SYS"."INCEXP" TO "SYF"
GRANT REFERENCES ON "SYS"."INCEXP" TO "SYF"
GRANT SELECT ON "SYS"."INCEXP" TO "SYF"
GRANT UPDATE ON "SYS"."INCEXP" TO "SYF"
GRANT ALTER ON "SYS"."INCFIL" TO "SYF"
GRANT DEBUG ON "SYS"."INCFIL" TO "SYF"
GRANT DELETE ON "SYS"."INCFIL" TO "SYF"
GRANT FLASHBACK ON "SYS"."INCFIL" TO "SYF"
GRANT INDEX ON "SYS"."INCFIL" TO "SYF"
GRANT INSERT ON "SYS"."INCFIL" TO "SYF"
GRANT ON COMMIT REFRESH ON "SYS"."INCFIL" TO "SYF"
GRANT QUERY REWRITE ON "SYS"."INCFIL" TO "SYF"
GRANT REFERENCES ON "SYS"."INCFIL" TO "SYF"
GRANT SELECT ON "SYS"."INCFIL" TO "SYF"
GRANT UPDATE ON "SYS"."INCFIL" TO "SYF"
GRANT ALTER ON "SYS"."INCVID" TO "SYF"
GRANT DEBUG ON "SYS"."INCVID" TO "SYF"
GRANT DELETE ON "SYS"."INCVID" TO "SYF"
GRANT FLASHBACK ON "SYS"."INCVID" TO "SYF"
GRANT INDEX ON "SYS"."INCVID" TO "SYF"
GRANT INSERT ON "SYS"."INCVID" TO "SYF"
GRANT ON COMMIT REFRESH ON "SYS"."INCVID" TO "SYF"
GRANT QUERY REWRITE ON "SYS"."INCVID" TO "SYF"
GRANT REFERENCES ON "SYS"."INCVID" TO "SYF"
GRANT SELECT ON "SYS"."INCVID" TO "SYF"
GRANT UPDATE ON "SYS"."INCVID" TO "SYF"
GRANT EXECUTE ON "SYS"."SET_TABLESPACE" TO "SYF"
GRANT ALTER ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."X$PT4PA7MVGH9J9E2BE328FS4HIHF4" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$ACL" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$CHECKOUTS" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$CONFIG" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$D_LINK" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$H_INDEX" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$H_LINK" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$NLOCKS" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$RESCONFIG" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$RESOURCE" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XDB$WORKSPACE" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XS$DATA_SECURITY" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XS$PRINCIPALS" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XS$ROLESETS" TO "SYF" WITH GRANT OPTION
GRANT ALTER ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT DEBUG ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT DELETE ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT FLASHBACK ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT INDEX ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT INSERT ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT ON COMMIT REFRESH ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT QUERY REWRITE ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT REFERENCES ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT SELECT ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT UPDATE ON "XDB"."XS$SECURITYCLASS" TO "SYF" WITH GRANT OPTION
GRANT "AQ_ADMINISTRATOR_ROLE" TO "SYF" WITH ADMIN OPTION
GRANT "CONNECT" TO "SYF"
GRANT "DBA" TO "SYF" WITH ADMIN OPTION
GRANT "MGMT_USER" TO "SYF"
BEGIN
dbms_resource_manager_privs.grant_switch_consumer_group(
grantee_name => 'SYF',
consumer_group => 'SYS_GROUP',
grant_option => FALSE
END;
BEGIN
dbms_resource_manager.set_initial_consumer_group(
user => 'SYF',
consumer_group => 'SYS_GROUP'
END;

HT4796 I did all of the above and the migration was successful, but I don't know where the files are. It says they're under a different user, 'owner' . I tried to access via sys pref/system/users&groups, but it asks for a password for owner which I don'

Migration Assit , PC to MAC - The migration was successful, but I don't know where the files are. It says they're under a different user, 'owner' . I tried to access via sys pref/system/users&groups, but it asks for a password for owner which I don't have. What must I do to access my files?
My experience is with MS PC's I'm new with the MAC Book Pro.

Then, see if this works:
Mac OS X 10.6 Help- If you forget your administrator password
If you are running Lion or Mountain Lion you may need to do the following to access the same utility:
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
When the menubar appears select Terminal from the Utilities menu. Enter resetpassword at the prompt and press RETURN. Follow instructions in the dialog window that will appear.
Or see Reset a Mac OS X 10.7 Lion Password and OS X Lion- Apple ID can be used to reset your user account password.

After recording text using the dragon dictation app, it is converted, it can be copied to the iOS system clipboard for use in any app, how does the user access the clipboard to retrive this information if it is no longer on the screen?

after recording text using the Dragon dictation app, it can be copied to the iOS systme clipboard for use in any app, how does the user access the clipboard to retrive this information if it is no longer on the screen?

You need to do a long-press in any data entry field, then select Paste.

Project Server 2010 PWA Provisioning Error - System.UnauthorizedAccessException: Access is denied.

Hi,
When migrating from a Prod Environment to a Test Environment using the Project Server 2010 5 Database backup and restore process (actually 6 DB's with the Project Sites DB), upon encountering a failure during provisioning the PWA Instance, we get the errors listed
at the base of this posting in our Event Logs.
To clarify what we have done already, we have:
1. Backed up the 6 databases from the Source Environment.
2. Removed the existing PWA_Content and PWS_Content (Project Sites) databases from the Target Environment Farm.
3. Restored the 6 databases in the Target Environment.
4. Given the SP Farm Service Account 'db_owner' rights to each of the 6 restored databases.
5. Added the PWA_Content and PWS_Content databases (exact same names) to the Target Environment.
6. Locked down (offline/stopped), all of the SharePoint Content databases in the Farm except for the PWA_Content database.
7. Run the PWA Provisioning process from the 'Project Server' SharePoint Service in Central Admin.
It is during the PWA provisioning that we encounter these errors.
As the Target Environment is for Test/Dev purposes, the SP Farm Service Account is setup to support all of the SharePoint Farm Services, is in the Local Admin Group of each of the Servers (App, WFE and DB), and is actually in the sysadmin
role on the DB Server.
Any suggestions on what is causing this denied access situation would be most appreciated.
Cheers,
Wayne
Event Log Entries:
============================================
Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/22/2014 2:47:34 PM
Event ID:      6971
Task Category: Provisioning
Level:         Error
Keywords:
User:          ACCOUNTS\svc_psfarm
Computer:      SERVER.accounts.domain.com
Description:
Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Membership synchronization failed. ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at Microsoft.SharePoint.Library.SPRequest.AddRoleDef(String bstrUrl, String bstrName, String bstrDescription, Boolean bHidden, Int32 lRoleOrder, UInt64 iPermMask, Byte iType, Int32 lRoleDefID)
   at Microsoft.SharePoint.SPRoleDefinitionCollection.AddCore(SPRoleDefinition role)
etc....
Failed to create the Report Center web (Exception: PSI Entry Point:
Project User: DOMAIN\svc_psfarm Correlation Id: c0a30b18-46e4-4447-b469-f8fd3bb1490a
PWA Site URL: http://pstest2010/PWA
SSP Name: Project Server
PSError: NoError (0))
Failed to grant 'DOMAIN\svc_psfarm' access to web application 'SPWebApplication Name=Portal'.
Error: System.Security.SecurityException: Access denied. Only machine administrators are allowed to create administration service job definitions of type: Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup, Microsoft.SharePoint, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c.
   at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition..ctor(String name, SPService service, SPServer server, SPJobLockType lockType)
   at Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup..ctor(SPTimerService timerService, String[] loginsToAdd, String[] loginsToRemove)
   at Microsoft.SharePoint.Administration.SPWebApplication.GrantAccessToProcessIdentity(String username, SPPolicyRoleType policyRole)
   at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GrantAccessToWebApp(List`1 webApps, String userName) The Zone of the assembly that failed was: MyComputer

Is the Test and Production in the same domain. If they are not, then the SIDs associated with the SQL accounts may look the same but they are not. At times, I have had to recreated accounts when in different domains.
I would also use PowerShell cmdlets and see if it finds any issues, such as Test-SPContentDatase.. Validate the SharePoint content databases, because if not setup properly the Provisioning will fail.
Also check these properties.
$web=get-spweb http://prodproj01/pwa
$Web.AllProperties[“PWAURL”] ### see what the value is.. you may have to blank it out, specially if it is pointing to a different URL
Here is how to fix.
$Web.AllProperties[“PWAURL”]=””
$web.Update()
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

ST03N shows users accessing transactions even when not logged in

Hello all...
We are trying to determine how many times a user executed a transaction during a specific period, and are using ST03N to do this.
We get the information fine, but it shows non-system users as having accessed transactions on days they are not logged in or it shows excessive use of a transaction (i.e 8000 times in a 20 day period).
We have confirmed that no batch jobs or system jobs are running or have run under their ID's. Additionally, it shows use of transactions which the users are not authorized to use.
Please help as we are trying to explain this for SOX purposes.
Cheers all!
Joe Johnson

Thanks for the replies...
We can use AL08, but it doesn't show any user activity for the specific users that keep popping up in ST03N.
RFC calls seem to be closest to explaining this, but how can one track the calls made by a user? Additionally, if the ID is not authorized to perform a transaction shouldn't the RFC call fail?

Can two users access the same bootcamp (win os) instance?

We are two users who are using our imac and we both have own user names in mac os. I created a bootcamp partition with windows xp on it. Can both users access the same partition and create their own user spaces within xp?
Will that work also if we use Parallel or virtual box? (access the same user data as in boot camp?)
I would like to have the option for each user to access their windows data either through bootcamp or through the virtual tool.
Message was edited by: gss2
Message was edited by: gss2

gss2 wrote:
What do you mean Virtual box it will not run on its own partition? I have a virtual box running on my desktop and it runs just fine ...own partition?? I don't understand.
Running on its own partition means that the installed OS has its own formatted portion (partition) of the hard drive. A virtual machine does not have its own partition. It creates a virtual partition (a file on the computer) that simulates a file system (partition). So Virtual Box, or any other virtualization software, does not run Windows, or any other OS in its own partition.

Multiple User Accessing the same record issue

I am planning to design an app where we have the following use case requirement.
If a user who is logged into the system is accessing a record(plan in this case) anyone else who is logged into the system at the same time should be locked out of that same plan but should still be able to access other plans in the system. A plan has many things associated with it so the 2nd user should be locked out of everything associated to the plan being accessed by the first user.
What is the best way to implement this at the application or the database level?
Here are some options we have been bouncing around.
1. When the first user logs in and accesses the first plan we lock the plan at the app level using a singleton class which has one and only one instance on the app server. The plan_id can be put as an entry into a hashtable which can be in the session and is created if one does not exist. When the 2nd user tries to access the same plan, since the plan_id is still in the hashtable he would be locked out. However we somehow need to timeout the first user after 30 mts of inactivity or so so that others can access the plan and are not locked out for ever if the first user walks away from his PC or does not close his browser, thus keeping his session alive indefinitely.
2. In the database in the plan table we add a column for 'locked'. When the first entry is created in the plan table locked column is marked as 'yes' or 1 and when the user closes the browser we use some javascript to trigger an event which changes that 'yes' or 1 to 'no' or 0 thus unlocking the plan. However the big issue we see in this concept is that we will have to put a javascript onUnload method in all jsp pages in the app because the user could be anywhere in the app after starting his plan access after login.
Conceptually the 2 options are the same but one is done at the app whereas the other is at the database level.
Is there a better way to handle this scenario using transactions or some other technological option.
Thanks

Another solution involving no modification of the database structure:
As soon as a user want to access a plan, try to UPDATE the plan record... if it fails, the record was locked
by another user before. When the user has finished with the plan, you can COMMIT or ROLLBACK the changes, which will free the lock for other users.
An advantage of this solution is that if program crashes unexpectedly, there will automatically be a ROLLBACK.
Of course, you need a transaction for this... and perhaps more if you want to separate the 'locking transaction' (virtual update just for restricting access) from the 'operating transaction' (in which you will
do the DB stuff: inserts, updates, deletes, etc.)
Hope this helped,
Regards.

Problem with users accessing sharepoint 2013 site collection

I have an unbeliveable problem..
I have a sp site with several site collections..
I have around 15 users.. Everybody have access to the root site. Two users do not have access to site collections even though they are in EXACTLY same permission groups like other users who can access those site collections!
I tried to delete them from all user groups in SP, then delete their user profiles in Central Administration, and delete them from Active Directory. After that I recreated their profiles in Active directory, readded them to Central Administration, and again
added them to coresponding groups in SharePoint site collections. They again CAN NOT ACCESS site collections.
What should I do.. This is incredible that 5 users with the same user privileges can access site collections, and 2 can not, even though they are all created in the same way..
Regards,
Srdjan

Hello,
Have you found a solution for this problem? I have the exact same problem with 2 users accessing a site collection (access denied). I found also this row on uls log:
Access Denied. Exception: Attempted to perform an unauthorized operation., StackTrace:   at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)     at Microsoft.Office.Project.PWA.PJBaseWebPartPage.OnPreInit(EventArgs
e)     at System.Web.UI.Page.PerformPreInit()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionSt... 6955b79c-c42c-50fc-84f8-2b68f97002ea

How do I get system users/groups to appear in the Workgroup Manager list?

When I open the Workgroup Manager and select the Users tab, it only shows users set up in the Workgroup Manager -- same when I browse Groups. But, I also have a couple system users/groups set up not in the workgroup manager, but through the OS's System Preference interface for Users.
Is there a way to automatically have System users appear in the Workgroup list?
I also can't add users to System groups, since the groups also won't appear in the Workgroup Manager (like adding a user to the group Admin or Staff -- default system groups).
I'd just like the option to "show System users and groups" somewhere.
Thanks.
Patrick

Hi
If I understand your post correctly then launch WorkGroup Manager and select Preferences from the WorkGroup Manager Menu. Enable the Show "All Records" tab and inspector option and click OK. In the Users/Groups/Computer tab you should now see the addition of another icon - it looks like a bullseye. Select this and under the filter field selecting 'AccessControls' will show you a long list. Scroll down and select Users. Now go back to the Users tab and you should see all users visible and invisible. You’ll see the same thing for Groups.
You will see different Users and Groups depending which directory node you are in. In the LDAP node you should only see Directory and System Administrator as well as VPN MPPE Key Access User in addition to any user you have created within that node. In the local Net Info node you should see users such as Amavisd User, Clamav User, Cyrus IMAP User etc. You’ll also see UIDs and GUIDs amongst a wealth of other information if you select a user or group and select the Inspector tab.
You can modify record attribute and values as well as adding your own. You can even use WGM in the same way you would use Net Info Manager locally if you wish.
Tony

File Permissions on Oracle Directories for other Operating System Users

Hi,
I am trying to export the table data to flat file using a pl/sql function using UTL_FILE package and directories created using 'CREATE DIRECTORY' command. The function is called from a stored procedure which in-turn is called from a Java program using JDBC and the Java process runs as different operating system user. The problem for me is the file exported is being written as 'ORACLE' user with 'OINSTALL' group and '-rw-r--r--' linux file permissions. When I try to read this exported file from the java program it throws me a file access error.
I would like to know if we can specify any additional parameters either in
1) Database parameter file
2) UTIL_FILE.FOPEN function
3) CREATE DIRECTORY command
so that the files written to the DIRECTORY have a read write access.

Since you attempting to read the file from Java, you are constrained by the OS.
Write a stored proc to read the file, since PL/SQL does have the correct permissions to read/write to files.
P;

Permissions for Linux user accessing Leopard share

We have a very simple networking setup at our video post production facility. Basically, files are shared everywhere and to everyone. No open directory or DNS serving. Just AFP and SMB.
Our Linux based Smoke/Flame/Lustre system needs access to the files severed/shared by an Xserve with a big attached RAID. It has no problem connecting or seeing the files. However, it typically is denied write permissions. When the Smoke operator creates a folder on the share he can't access the folder until I grant the Others/Everyone group read and write perms. The Linux user logs in with the same user account that everyone else uses.
Some time ago, the always smashing Gerrit DeWitt gave me some terminal commands to set ACLs for users/groups of this shared RAID. They work beautifully and I have had no permissions issues since applying them. Except for this Linux system.
Would it be good practice to use this command to set the Everyone group permissions for this share?
sudo chmod -R +ai "group:everyone allow readattr,readextattr,readsecurity,\
list,search,read,execute,writeattr,writeextattr,delete,\
append,write,deletechild,add_file,addsubdirectory,\
fileinherit,directoryinherit" "/Volumes/RAIDH/Smoke_InfernoStorage"
Also, is there some configuration change I could make to the Linux system to make it a little more Mac compatible in this area?
Thanks

It's worth checking into - let us know what you find. What you describe certainly sounds like a problem with permission propagation settings for SMB / Samba since the AFP side works fine.
I've seen other posts about problems that crop up because of differences in the versions of Samba employed between systems, so that's a possibility as well. And I'd have no suggestions for you in that regard other than some searching of the web for clues as to how to work with that issue.
-Doug

Re: (forte-users) access violation caught in debugmode

Eric,
There has been a problem with Forte debug mode for sometime now when the app
is silent. If you attempt to inspect the variables when the app is in the
'silent' mode, i.e., waiting on an event loop for a user input or a system
event, then you get the "Access violation caught ..." exception message and
the workspace including the launch server crashes.
If you are getting this problem in the 'step-through' mode, you should look
at the lauch server immediately after you get the exception before
everything disappears. There could be a stack backtrace due to some illegal
reference. We have faced a similar situation before but the error appeared
both in the 'debug' and 'run' modes.
Hope this helps.
Braja K Chattaraj.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

Eric,
Another possibility has to do with the repository. You said you recently
migrated 30G2 to release 30L2.
Many strange problems have been traced to release migrations with old
repositories. If the repository was properly migrated another thing you can try
is to export the project(s) to PEX files, delete them from the repository, and
then re-import. I know this can be time consuming but I have solved more than
one unexplained problem in the IDE by doing it.
---------------------- Forwarded by Charlie Shell/Bsg/MetLife/US on 09/23/99
01:19 PM ---------------------------
"Ajith Kallambella" <[email protected]> on 09/23/99 12:08:54 PM
To: [email protected], [email protected]
cc: (bcc: Charlie Shell/Bsg/MetLife/US)
Subject: Re: (forte-users) access violation caught in debug mode
Eric,
Sometimes( 90% ) you can solve this problem by
checking out the class that is causing the crash
and force-compiling it.
If it doesn't help, run through this checklist.
1. Do you have enough memory resources.?
2. Is the object you are inspecting held in a lock ?
( mutex, transaction lock etc )
3. Does it work when you wait for sometime at the
breakpoint before inspecting the values? I mean
are you interrupting some process thread?
4. Does it work if you log the attributes using logmgr?
5. Are you using any call-outs/call-ins? Any external
systems integration? Sometimes( for reasons beyond
my comprehension ) the objects allocated outside
Forte gets corrupted when its passed back and forth.
6. ...finally...Santa Clause, help me!
Ajith Kallambella M.
Forte Systems Consultant.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

System User access?

Similar Messages

Maybe you are looking for