**→ OS: Oracle Linux Server release 8.7** **→ DBMS: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production - Version 19.3.0.0.0** After cloning a virtual machine that we can connect normally on sqlplus with sys user, we cannot say the same about the clone and reconfigured machine, even change sys password and putting the right one: > oracle@somedb ~]$ sqlplus sys@somecdb as sysdba > > SQL*Plus: Release 19.0.0.0.0 - Production on Seg Set 23 09:39:55 2024 > Version 19.3.0.0.0 > > Copyright (c) 1982, 2019, Oracle. All rights reserved. > > Informe a senha: ERROR: ORA-01017: senha/nome do usu�rio inv�lido; > log-on negado But I can connect with SYSTEM user and probably with the other users, on both machines: > oracle@somedb ~]$ sqlplus system@somecdb > > SQL*Plus: Release 19.0.0.0.0 - Production on Seg Set 23 09:56:01 2024 > Version 19.3.0.0.0 > > Copyright (c) 1982, 2019, Oracle. All rights reserved. > > Informe a senha: Hor�rio do �ltimo log-in bem-sucedido: Seg Set 23 > 2024 09:03:09 -03:00 > > Conectado a: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 > - Production Version 19.3.0.0.0 > > SQL> The root connection is ok (sqlplus / as sysdba), but the CDB connection not - same problem happens trying to connect with SQL Developer. How can I solve it?

**In the past** : When I had once the error ORA-00257: Archiver error, I had resolved it using the RMAN command: rman target sys/1234 delete archivelog all; **This time** , **when I try to connect to rman target**: rman target sys/1234 I get the error: RMAN-00554: initialization of internal recovery manager packagefailed. RMAN-04005: error from target database. ORA-28001:the password has expired. **When I try to connect with sqlplus as sys SYSDBA**, then raises the following error: ERROR: ORA-28001: the password has expired Changing password for SYS New password: **When I type the new password**, the error that comes is: ORA-00257: Archiver error. Connect AS SYSDBA only until resolved. So the problem is that.. - When I connect through sqlplus as sys SYSDBA, I cannot change the expired sys password because of archivelog RMAN. - When I try to fix RMAN error, I cannot connect to RMAN due to the expired sys password. How can I solve this?

I am using Oracle 12c on Linux. Using the enterprise manager database express, I am looking at the list of privileges and roles for the SYS user but I haven’t found the SYSDBA privilege assigned there. Is the SYS user a member of an Oracle role or Linux group with sysdba privilege? If so, which role or group?

If the SYSDBA privilege gives the grantee ultimate authority, then why does the SYS user also have the DBA role in addition to the SYSDBA privilege?

I don't know if I correctly understand the privileges of these built-in roles and users, but this is a list of the information that I have found: * The DBA and SYSDBA roles enable you to do everything. If this is true, then why are there two names for the same thing? * The SYSOPER role enables you to do everything except accessing users' data; * The SYS user has the DBA and SYSDBA roles, so they can do anything; * The SYSTEM user has the DBA role, so it seems that they could do anything, but I have read that they cannot do backups, recovery, and DB upgrade. Is my understanding correct?

There are two ways to connect to Oracle as an administrator using SQL Plus: 1. sqlplus sys as sysdba 2. sqlplus system/manager These accounts should be used for different purposes, I suppose. Which tasks are these two schemas meant for? When should I use one over the other?

The reason I'm asking is because I need to install the sys schema on my database so that I can utilize performance_schema because I'm hoping that will help me figure out why mysql is crashing every 30 minutes exactly. I am running MySQL 5.5.45 on Windows Server 2016. I have four schemas on this server, of which the production schema is 4.1GB in size. The other schemas are almost as big. MySQL Workbench gives me an option to install it. Also, I understand that running mysql_upgrade will install it, which as far as I can tell simply executes mysqlcheck. So it looks like I have three options for installing the sys schema. - Execute mysqlcheck (I think) - Execute mysql_upgrade - Click the install button on MySQL Workbench What does MySQL Workbench do exactly? Does it simply execute mysql_upgrade or mysqlcheck? Or does it do the install a different way? Will any or all of these options make my other schemas unusable while this install is executing (as in locking tables)? What other implications are there to using any of these three options? And most importantly, needing to install this on a production server, what is my best approach?

I would like to know what GRANT is required to block the SYS user, as i have a common user in the database. GRANT ALTER USER enabled me to block only the SYSTEM, but it returns the error ORA-01031: insufficient privileges when trying to block the SYS account. I have also tried GRANT SYSOPER, but also without success.

Our identity management tool wants to change the sys password regularly. It fails with the ORA-01031. What privileges or roles do I need to grant the identity management tool user to be able to change the sys password?

By mistake I deleted by-default saved 'sys' database in Mysql version 8.0.21 So, how to restore it?

I want to create a trigger for CRE schema. I'm trying to create this trigger with SYS user but I have insufficient privileges error. My trigger: CREATE OR REPLACE TRIGGER CRE.TRIGGER_NAME AFTER LOGON ON DATABASE DECLARE asd1 NUMBER; asd2 NUMBER; asd3 NUMBER; asd4 NUMBER; asd NUMBER; qwe VARCHAR2(200); qaz VARCHAR2(200); ewq NUMBER; zaq VARCHAR2(50); xsw VARCHAR2(50); BEGIN CRE.SOME_PROCEDURE_NAME('S', SYSDATE); END; / How can it possible with SYS user? How can I fix it? Best regards.

Hi i have a question but not sure what the problem was and how it happened though. The initial error when i logged in the DB dev machine was ORA-00942: table or view does not exists. Some of the system views that we tried to access gave a ORA-017775: looping chain of synonyms. Then we noticed some of the ALL_* and DBA_* views and functions were missing, which were causing alot of the dependencies and system packages to throw errors. We also noticed that the SYSTEM tablespace has reached 100% utilized space. So my question is, is it possible when the SYSTEM tablespace runs out of space, it would randomly drop the SYS views and functions We also checked the alert logs, seems like it happened during a non-working period. Or is there any logs that i could further check on what happened that caused SYS views and functions being dropped suddenly ? Regards, Thanks

As far as I know the resource database contains information on all objects in its server instance, so I would think it's only natural that when you restore a database from a backup file, part of the process would be to register its objects in the server's resource database but I can't find any concrete information on the subject and I'm unable to test it locally.

using mysqldump while doing a backup gives the following error: mysqldump: Got error: 1356: "View 'sys.host_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them" when using LOCK TABLES What can I do to fix that?

When I run SELECT OBJECT_DEFINITION(OBJECT_ID('sys.assembly_files')); I can see that there is a self-join on sys.sysobjvalues, but when I try to select that table I get, Msg 208, Level 16, State 1, Line 1 Invalid object name 'sys.sysobjvalues'. What's going on here? Why is that object name invalid?