InfoLipi

  Basic Rsync Script For Transferring Or Synchronizing Files From One Server (SourceSrv) To Another Server (DestinationSrv) Source Host: SourceSrv                                                         Destination Host: DestinationSrv LogIn on DestinationSrv: mkdir -p /home/rony/.scripts/ touch /home/rony/.scripts/rsync.sh touch /home/rony/.scripts/rsync.log chmod u+x /home/rony/.scripts/rsync.sh For killall command install: sudo dnf search psmisc tee /home/rony/.scripts/rsync.sh >/dev/null <<EOF #!/bin/bash ################################################################################################################## export Script=/home/rony/.scripts/ export Source=rony@SourceSrv: /data/docs/ export Destination= /data/docs/ export LogFile=${Script}/rsync.log echo 'Source : '${Source} 2>&1 | tee -a ${Script}/rsync.log echo 'Destination : '${Destination} 2>&1 | tee -a ${Script}/rsync.log ########################

Bash Script For Transferring Or Synchronizing RMAN Backup Files From One Server (SourceSrv) To Another Server (DestinationSrv) And Deleting Old RMAN Backup Files Source Host: SourceSrv                                                         Destination Host: DestinationSrv LogIn on DestinationSrv: mkdir -p /home/rony/.scripts/ touch /home/rony/.scripts/rsync.sh touch /home/rony/.scripts/rsync.log chmod u+x /home/rony/.scripts/rsync.sh For killall command install: sudo dnf search psmisc tee /home/rony/.scripts/rsync.sh >/dev/null <<EOF #!/bin/bash ################################################################################################################## export Script=/home/rony/.scripts/ export Source=rony@SourceSrv:/u01/rman_backup/ export Destination=/u01/db_backup/backup_from_DestinationSrv/rman/backup_files/ export LogFile=${Script}/rsync.log echo 'Source : '${Source} 2>&1 | tee -a ${Script}/rsync.log echo 'Desti

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. 1.0. error message: Error Message: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. Pass in a valid hostname and port number for the OMS to successfully deploy the agent. 1.1. deploy log: Log: /opt/gc_inst/em/EMGC_OMS1/sysman/agentpush/2023-11-07_16-09-23-PM/applogs/dblivesrv_deploy.log Execution of command cd /opt/agent/ADATMP_2023-11-07_16-09-23-PM;/opt/agent/ADATMP_2023-11-07_16-09-23-PM/agentDeploy.sh -ignorePrereqs ORACLE_HOSTNAME=dblivesrv AGENT_BASE_DIR=/opt/agent OMS_HOST=oemsrv.localdomain EM_UPLOAD_PORT=4903 AGENT_INSTANCE_HOME=/opt/agent/agent_inst b_doDiscovery=false START_AGENT=false b_forceInstCheck=true -force AGENT_PORT=3872 on host dblivesrv Failed 1.2. oms details: [oracle@oemsrv ~]$ $OMS_HOME/bin/emctl status oms -details Oracle Enterprise Manager Cloud Control 13c Release 5 Copyright (c) 1996, 2021

The problem as stated: After upgrading the Oracle Database from 12c to 19c the following error generated in the alert log file. Actual Oracle Error Code: ORA-00800 After Upgrading from 12c to 19c ORA-00800: soft external error, arguments occured Oracle Database Enterprise 19c fails to start with error: ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM] Why does Insights prevent Oracle grid services from starting How to configure the User slice to allow Real-Time Scheduling for user processes In Alert Log: Errors in file /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/trace/psbcdb_vktm_3529.trc (incident=1200048) (PDBNAME=CDB$ROOT): ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM], [Check traces and OS configuration], [Check Oracle document and MOS notes], [] Incident details in: /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/incident/incdir_1200048/psbcdb_vktm_3529_i1200048.trc 2023-10-30T10:04:53.536165+06:00 Error attempting to elev

Overview Oracle Database 19c is a multi-model database that provides full support for relational and non-relational data, such as JSON, XML, text, spatial and graph data. There are lots of new features available in this new release like partitioned hybrid tables, encryption capabilities in the built-in data dictionary, statistics-only queries and many more. It also enables Oracle’s Autonomous Database Cloud Services. This article describes the installation of Oracle Database 19c (19.3) 64-bit on Red Hat 8 64-bit. When you plan to upgrade from 12c to 19c that means, you have already some configuration when you install 12c. So, this software-only installation will be minimal. Lab Environment Server Machine Work Station or Client Machine OS Release Red Hat Enterprise Linux release 8.4 (Ootpa) Red Hat Enterprise Linux release 8.4 (Ootpa) Kernel 4.18.0-305.3.1.el8_4.x86_64 4.18.0-305.7.1.el8_4.x86_64 Oracle Release 19.3 Oracle SQL Developer Version 19.2.1.247 IP Address 192.168.1.10 192.168

 ORA-01950: no privileges on tablespace "TABLESPACE_NAME" Cause: User does not have privileges to allocate an extent in the specified tablespace. Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace. To control the amount of disk space that a user can consume in a tablespace, you can assign a quota to the user for that tablespace. A quota can be either a specific number of bytes, a percentage of the total space in the tablespace, or unlimited. To grant a quota, you can use the following syntax: ALTER USER username QUOTA { size | UNLIMITED | DEFAULT } ON tablespace_name; For example, to give user Alice 100 MB of space in the tablespace TBS1, you can write: ALTER USER Alice QUOTA 100M ON TBS1; Or you can give unlimited quota to user on related tablespace as follows. ALTER USER <user> quota unlimited on <tablespace name>; Or you can give unlimited quota to user on all tablespace as follows. GRANT UNLIMITED TABLES

Naming Conventions of Oracle Database About Assigning Global Database Names During Installation The database name input field is used to set the DB_NAME, DB_UNIQUE_NAME, and DB_DOMAIN Oracle initialization parameter values. The Oracle Database software identifies a database by its global database name. A global database name consists of the database name and database domain. Usually, the database domain is the same as the network domain, but it need not be. The global database name uniquely distinguishes a database from any other database in the same network. You specify the global database name when you create a database during the installation or using the Oracle Database Configuration Assistant. For example: sales.us.example.com Here: sales.us is the name of the database. The database name, DB_UNIQUE_NAME, portion is a string of no more than 30 characters that can contain alphanumeric characters, underscore (_), dollar sign ($), and pound sign (#) but must begin with an alphabetic c