By using AWS re:Post, you agree to the Terms of Use
/Oracle/

Questions tagged with Oracle

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

RDS custom oracle disk full

Hello We are currently using AWS RDS Custom Oracle and the OS disk have a root partition of 10Gb , although allocating a 42 Gb volume . Just to add a cherry atop, there is a 16Gb swap area allocated in between, which make worse to expand to the remaining disk area I could barely get out of os disk full condition killing old log files in /var/log [root@ip- /]# df -kh Filesystem Size Used Avail Use% Mounted on devtmpfs 7.6G 0 7.6G 0% /dev tmpfs 16G 7.5G 7.8G 49% /dev/shm tmpfs 7.7G 785M 6.9G 11% /run tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup /dev/nvme0n1p1 9.8G 7.9G 1.8G 83% / /dev/nvme1n1 25G 13G 11G 54% /rdsdbbin /dev/mapper/dbdata01-lvdbdata01 296G 25G 271G 9% /rdsdbdata tmpfs 1.6G 0 1.6G 0% /run/user/61001 tmpfs 1.6G 0 1.6G 0% /run/user/61005 [root@ip- aws]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 42G 0 disk ├─nvme0n1p1 259:1 0 10G 0 part / ├─nvme0n1p128 259:3 0 1M 0 part └─nvme0n1p127 259:2 0 16G 0 part [SWAP] nvme3n1 259:6 0 75G 0 disk └─dbn0-lvdbn0 252:0 0 300G 0 lvm └─dbdata01-lvdbdata01 252:1 0 300G 0 lvm /rdsdbdata nvme2n1 259:5 0 75G 0 disk └─dbn0-lvdbn0 252:0 0 300G 0 lvm └─dbdata01-lvdbdata01 252:1 0 300G 0 lvm /rdsdbdata nvme5n1 259:8 0 75G 0 disk └─dbn0-lvdbn0 252:0 0 300G 0 lvm └─dbdata01-lvdbdata01 252:1 0 300G 0 lvm /rdsdbdata nvme1n1 259:4 0 25G 0 disk /rdsdbbin nvme4n1 259:7 0 75G 0 disk └─dbn0-lvdbn0 252:0 0 300G 0 lvm └─dbdata01-lvdbdata01 252:1 0 300G 0 lvm /rdsdbdata du -sh ./*/ 185M ./bin/ 143M ./boot/ 7.5G ./dev/ 43M ./etc/ 124K ./home/ 1.1G ./lib/ 195M ./lib64/ 16K ./lost+found/ 4.0K ./media/ 4.0K ./mnt/ 3.4G ./opt/ 0 ./proc/ 13G ./rdsdbbin/ 25G ./rdsdbdata/ 13M ./root/ 785M ./run/ 46M ./sbin/ 4.0K ./srv/ 0 ./sys/ 72K ./tmp/ 465M ./usr/ 2.5G ./var/ What im planning to do is to allocate a new swap volume , switch it on, kill the old swap and expand the original volume as the most i could. 1) Could this harm any monitoring task in AWS for RDS custom? 2)Any good soul at AWS could look into the automation scripts for RDS custom and make SWAP on a separate volume? , and allocate the 42Gb volume fully for OS? There can happen some bad stuff any OS updates that surely need more disk space
0
answers
0
votes
8
views
asked 6 hours ago

How to configure Glue Connection to successfuly connect to Oracle RDS Using NNE (Not SSL)

As part of our migration to AWS, we've created an Oracle RDS that is configured for Native Network Encryption.... No SSL Oracle Option Group: ``` SQLNET.ALLOW_WEAK_CRYPTO true SQLNET.ALLOW_WEAK_CRYPTO_CLIENTS true SQLNET.CRYPTO_CHECKSUM_CLIENT REQUESTED SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT SHA512, SHA384, SHA256 SQLNET.ENCRYPTION_CLIENT REQUESTED SQLNET.ENCRYPTION_TYPES_CLIENT RC4_256, AES256, AES192, 3DES168, RC4_128, AES128, 3DES112, RC4_56, DES, RC4_40, DES40 SQLNET.ENCRYPTION_SERVER REQUIRED SQLNET.ENCRYPTION_TYPES_SERVER AES256 SQLNET.CRYPTO_CHECKSUM_SERVER REQUIRED SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER SHA256 ``` I've tried several different formatted JDBC URLs... without success... (Like adding ?crypto_checksum_client=required&crypto_checksum_types_client=sha256 to the JDBC URL) DMS Seems to have no issues connecting, but I cannot get a successful glue connection test. I have a PySpark Job that will need to connect back to the Oracle DB to run a quick query, but having issues connecting... all_pk_df = glue_context.read.format("jdbc") \ .option("url", jdbc_url) \ .option("dbtable", oracle_primary_keys_sql) \ .option("user", user) \ .option("password", password) \ .option("driver", 'oracle.jdbc.driver.OracleDriver') \ .load() I've tried setting options in the Python code as well, but haven't found the correct property as of yet... The issue seems to be with this: SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER SHA256 as when it was SHA1, connection was possible...
1
answers
0
votes
7
views
asked a month ago

Announcement: Amazon RDS for Oracle - End of Support Timeline for 12c Oracle Release 2 (12.2.0.1) and Oracle Release 1 (12.1.0.2) Major Version

Oracle Corporation has announced the end of support for Oracle Database version 12.1.0.2 on July 31, 2022, and version 12.2.0.1 on March 31, 2022 [1]. After these dates, Oracle Support will no longer release Critical Patch Updates for these database versions, and these versions will no longer be available in Amazon RDS for Oracle. For Oracle Database version 12.2.0.1: Amazon RDS for Oracle will end the support for Oracle Database version 12.2.0.1 (all editions) for both License Included (LI) and Bring Your Own License (BYOL) models on March 31, 2022. For Oracle Database version 12.1.0.2: Amazon RDS for Oracle will end the support for Oracle Database version 12.1.0.2 (all editions) for both License Included (LI) and Bring Your Own License (BYOL) models on July 31, 2022. If you have already upgraded your DB instance(s) to 19c, no further action is required. We highly recommend you upgrade your existing 12.1.0.2 and 12.2.0.1 DB instances to version 19c and validate your applications before the automatic upgrades begin. Please keep in mind the following timeline for the 19c version: • 19c: The Premier Support for Oracle Database 19c ends on April 30, 2024, while the Extended Support ends on April 30, 2027. Amazon RDS for Oracle plans to support Oracle Database 19c until April 30, 2027. 12.2.0.1 Deprecation - Timeline summary: • Now - March 31, 2022 - You can upgrade 12.2.0.1 DB instances manually to the version of your choice. • From February 14, 2022 - You can upgrade 12.2.0.1 snapshots manually to the version of your choice. • From February 14, 2022 - Amazon RDS for Oracle disables new instance creates on 12.2.0.1, but you will be able to continue to restore 12.2.0.1 DB snapshots without being auto upgraded until March 31, 2022. • From April 1, 2022 - Amazon RDS for Oracle starts automatic upgrades of 12.2.0.1 DB instances to 19c. • From April 1, 2022 - Amazon RDS for Oracle starts automatic upgrades to 19c of DB instances restored from 12.2.0.1 snapshots. 12.2.0.1 Deprecation Timeline by Amazon RDS for Oracle (for both BYOL and LI): Starting on February 14, 2022, Amazon RDS for Oracle will disable the ability to create new DB instances using 12.2.0.1. If you are using 12.2.0.1, please upgrade your instance(s) to a later major version before March 31, 2022. Starting on April 1, 2022, Amazon RDS Oracle will automatically upgrade DB instances from 12.2.0.1 to the latest Release Update (RU) on RDS for Oracle Database 19c. We highly recommend that you test your application on 19c or whichever major version you plan on upgrading to. Starting on April 1, 2022, any 12.2.0.1 DB instance created from a snapshot restore or point-in-time restore will be automatically upgraded to the latest RU on RDS for Oracle 19c. Starting on February 14, 2022, you may upgrade your snapshots manually from 12.2.0.1 to a newer major engine version. For more information, see Upgrading an Oracle DB Snapshot [3]. If you have encrypted snapshots do plan to perform manual snapshot upgrade. 12.1.0.2 Deprecation - Timeline summary: • Now - July 31, 2022 - You can upgrade 12.1.0.2 DB instances manually to the version of your choice. • From June 1, 2022 - You can upgrade 12.1.0.2 snapshots manually to the version of your choice. • From June 1, 2022 - Amazon RDS for Oracle disables new instance creates on 12.1.0.2, but you will be able to continue to restore 12.1.0.2 DB snapshots without being auto upgraded until July 31, 2022. • From August 1, 2022 - Amazon RDS for Oracle starts automatic upgrades of 12.1.0.2 DB instances to 19c. • From August 1, 2022 - Amazon RDS for Oracle starts automatic upgrades to 19c of DB instances restored from 12.1.0.2 snapshots. 12.1.0.2 Deprecation Timeline by Amazon RDS for Oracle (for both BYOL and LI): Starting on June 1, 2022, Amazon RDS for Oracle will disable the ability to create new DB instances using 12.1.0.2. If you are using 12.1.0.2, please upgrade your instance(s) to a later major version before July 31, 2022. Starting on August 1, 2022, Amazon RDS Oracle will automatically upgrade DB instances from 12.1.0.2 to the latest Release Update (RU) on RDS for Oracle Database 19c. We highly recommend that you test your application on 19c or whichever major version you plan on upgrading to. Starting on August 1, 2022, any 12.1.0.2 DB instance created from a snapshot restore or point-in-time restore will be automatically upgraded to the latest RU on RDS for Oracle 19c. Starting on June 1, 2022, you may upgrade your snapshots manually from 12.1.0.2 to a newer major engine version. For more information, see Upgrading an Oracle DB Snapshot [3]. If you have encrypted snapshots, you need to plan to perform manual snapshot upgrade. Additional Notes: After the upgrade, if the SQL statements perform in an unexpected manner due to the change in the plans by the 19c optimizer, you can use the OPTIMIZER_FEATURES_ENABLE parameter to retain the behavior of the 12c optimizer. There is no impact to your current Reserved Instances (RI) due to the engine version deprecation of 12.1.0.2 and 12.2.0.1. For versions in Extended Support, BYOL model customers must have purchased Extended Support agreements from Oracle Support or upgrade to a version for which they have support. For the details on the Licensing and Support requirements for the BYOL model customers, refer to the Amazon RDS for Oracle FAQs [4]. To learn more about upgrading Oracle major versions in RDS, review Upgrading the Oracle DB engine [5]. Please contact us through AWS Support [6] should you have any questions or concerns. Oracle Database Version 19c: The Extended Support for Oracle Database 19c ends on April 30, 2027. Amazon RDS for Oracle will support Oracle Database 19c until April 30, 2027. We recommend you to upgrade your existing 12.1.0.2 or 12.2.0.1 DB instances to version 19c [7] because it is the long-term support release. Note for versions in Extended Support, BYOL model customers must have purchased Extended Support agreements from Oracle Support or upgrade to a version for which they have support. For the details on the Licensing and Support requirements for the BYOL model customers, refer to the Amazon RDS for Oracle FAQs [4]. Review the version specific deprecation details on the AWS forum [2]. To learn more about Amazon RDS policy for supporting database versions, please see the RDS FAQs and search for “guidelines for deprecating database engine versions” [8]. Please contact us through AWS Support [6] or the AWS Developer Forums [9] should you have any questions or concerns. [1] https://www.oracle.com/us/assets/lifetime-support-technology-069183.pdf [2] https://forums.aws.amazon.com/ann.jspa?annID=8593 [3] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBSnapshot.Oracle.html [4] https://aws.amazon.com/rds/oracle/faqs/ [5] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Oracle.html [6] https://aws.amazon.com/support [7] https://aws.amazon.com/about-aws/whats-new/2019/11/amazon-rds-for-oracle-now-supports-oracle-database-19c/ [8] https://aws.amazon.com/rds/faqs [9] https://forums.aws.amazon.com/forum.jspa?forumID=60
0
answers
0
votes
73
views
asked a month ago

Announcement: Amazon RDS for Oracle - End of Support Timeline for DB snapshots

[Source: https://forums.aws.amazon.com/ann.jspa?annID=8848] **End of Support Timeline for DB snapshots on versions 11.2.0.2, 11.2.0.3 and 12.1.0.1** **Updated February 4, 2022** Extended the deletion timeline from Feb 15, 2022 to April 31, 2022. **Old DB snapshots Deprecation - Timeline summary:** • Now through April 31, 2022: You can upgrade 11.2.0.2, 11.2.0.3 and 12.1.0.1 DB snapshots manually to the supported snapshot versions. Please review the documentation for the supported upgrade paths [[1]]. • May 1, 2022: Amazon RDS for Oracle starts the automatic deletion of these old DB snapshots. **Updated October 20, 2021** Amazon RDS for Oracle deprecated 11.2.0.2, 11.2.0.3 and 12.1.0.1 database versions. As a result, we are deprecating the DB snapshots taken from these deprecated databases. If you currently have one or more Amazon RDS for Oracle DB snapshots, taken from the deprecated database versions. You must upgrade these old snapshots to ensure continued availability of these snapshots. **Old DB snapshots Deprecation - Timeline summary:** • Now through Apr 31, 2022: You can upgrade 11.2.0.2, 11.2.0.3 and 12.1.0.1 DB snapshots manually to the supported snapshot versions. Please review the documentation for the supported upgrade paths [[1]]. • May 1, 2022: Amazon RDS for Oracle starts the automatic deletion of these old DB snapshots. Additional Notes: For a step-by-step guide on how to update your DB snapshots, please review the Best Practices for upgrading Amazon RDS for Oracle DB snapshots blog [[2]] To learn more about upgrading an oracle DB snapshots, review the documentation [[1]]. Please contact us through AWS Support [[3]] or the AWS Developer Forums [[4]] should you have any questions or concerns. [[1]] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBSnapshot.Oracle.html [[2]] https://aws.amazon.com/blogs/database/best-practices-for-upgrading-amazon-rds-for-oracle-database-snapshots/ [[3]] https://aws.amazon.com/support [[4]] https://forums.aws.amazon.com/forum.jspa?forumID=60
0
answers
0
votes
15
views
asked 3 months ago

CodeBuild disconnects sqlplus

Hi all, I have created a test CodeBuild project which I want to connect to an RDS Oracle database and run a number of queries. I have a zip which contains sqlplus, the project retrieves this from S3, extracts the contents and sets the necessary paths and permission. I can then connect to the database, however straight after it has connected, it disconnects. Have I missed something here? Any help will be much appreciated! Thank you! **Build spec**: version: 0.2 phases: install: commands: - aws s3 cp s3://$MY_BUCKET/ . --recursive - dpkg -i *.deb - unzip sqlplus.zip - cd sqlplus - chmod +x sqlplus - export PATH=$(pwd):$PATH - export LD_LIBRARY_PATH=$(pwd):$LD_LIBRARY_PATH build: commands: - echo connecting to $ORACLE_USER/$ORACLE_PASSWORD@$ORACLE_ENDPOINT:$ORACLE_PORT/$ORACLE_DB - sqlplus $ORACLE_USER/$ORACLE_PASSWORD@$ORACLE_ENDPOINT:$ORACLE_PORT/$ORACLE_DB - SELECT * FROM dba_data_files; **Output from build log**: \[Container] 2021/08/20 09:32:03 Running command sqlplus $ORACLE_USER/$ORACLE_PASSWORD@$ORACLE_ENDPOINT:$ORACLE_PORT/$ORACLE_DB SQL*Plus: Release 21.0.0.0.0 - Production on Fri Aug 20 09:32:03 2021 Version 21.3.0.0.0 Copyright (c) 1982, 2021, Oracle. All rights reserved. Connected to: Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production Version 19.11.0.0.0 SQL> Disconnected from Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production Version 19.11.0.0.0 \[Container] 2021/08/20 09:32:03 Running command SELECT * FROM dba_data_files; /codebuild/output/tmp/script.sh: 4: SELECT: not found
1
answers
0
votes
0
views
asked 9 months ago

How to delete archive log file on Oracle RDS instance

We have an Oracle RDS instance that recently ran out of space with **ORA-01653** and **ORA-01654** (Unable to extend index ... by 8 in tablespace...) errors. On investigation by running query: ``` select nvl(sum(BLOCKS * BLOCK_SIZE),0)/1024/1024/1024 GB from V$ARCHIVED_LOG where DEST_ID=1 and ARCHIVED='YES' and DELETED='NO'; ``` This shows the output: ``` GB ---------- 26.3267608 ``` So we have 26 GB of Archive logs. Running the following query to get some info on the archive files: ``` select * from V$ARCHIVED_LOG where DEST_ID=1 and ARCHIVED='YES' and DELETED='NO'; ``` We have nearly 5000 rows of results. Some example rows: ``` RECID STAMP NAME DEST_ID THREAD# SEQUENCE# RESETLOGS_CHANGE# RESETLOGS RESETLOGS_ID FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME BLOCKS BLOCK_SIZE CREATOR REGISTR STA ARC APPLIED DEL S COMPLETIO DIC DIC END BACKUP_COUNT ARCHIVAL_THREAD# ACTIVATION# IS_ COM FAL END_OF_RED BAC ------ ---------- ------------------------------------------------------------ --------- ---------- ---------- ----------------- --------- ------------ ------------- --------- ------------ --------- ---------- ---------- ------- ------- --- --- --------- --- - --------- --- --- --- ------------ ---------------- ----------- --- --- --- ---------- --- 56851 1021006860 /rdsdbdata/db/DRGNFLY_A/arch/redolog-56852-1-1002024260.arc 1 1 56852 222206 04-MAR-19 1002024260 108023802 07-OCT-19 108025497 07-OCT-19 1721 512 ARCH ARCH NO YES NO NO A 07-OCT-19 NO NO NO 0 1 1073401855 NO NO NO NO 56852 1021007166 /rdsdbdata/db/DRGNFLY_A/arch/redolog-56853-1-1002024260.arc 1 1 56853 222206 04-MAR-19 1002024260 108025497 07-OCT-19 108026500 07-OCT-19 626 512 ARCH ARCH NO YES NO NO A 07-OCT-19 NO NO NO 0 1 1073401855 NO NO NO NO ``` The location of this archive file is: **/rdsdbdata/db/DRGNFLY_A/arch/redolog-56849-1-1002024260.arc** The other rows are also in this directory: **/rdsdbdata/db/DRGNFLY_A/arch** From: <https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.CommonDBATasks.Log.html> We have ran the stored proc: ``` exec rdsadmin.rdsadmin_master_util.drop_archivelog_dir; exec rdsadmin.rdsadmin_master_util.drop_onlinelog_dir; ``` This command executed but when running the query it still shows 23 GB of archive log files. To see the archive log retention config I ran: ``` set serveroutput on exec rdsadmin.rdsadmin_util.show_configuration; ``` This produces the output: ``` NAME:archivelog retention hours VALUE:0 DESCRIPTION:ArchiveLog expiration specifies the duration in hours before archive/redo log files are automatically deleted. NAME:tracefile retention VALUE:1440 DESCRIPTION:tracefile expiration specifies the duration in minutes before tracefiles in bdump are automatically deleted. ``` My questions: 1) Can you let us know how to remove this archive log files and reclaim the space so it can be used for normal DB storage etc. 2) Also how to make sure the log files do not continue to be generated or are cleaned up with an appropriate retention period.
1
answers
0
votes
22
views
asked 3 years ago

Download big Oracle DataPump-ImportFile from S3 fails

Hello, we have a big Oracle DataPump-ImportFile of about 165 GB in a S3-Bucket that we to import into a RDS Oracle 12.1 Database. The download begins but fails after having downloaded about 117 GB. RDS Database trace/alert.log from when it starts to fail: ``` Mon Jul 01 12:09:57 2019 WARN: ARCH: Terminating process hung on an operation (PID:16174) Mon Jul 01 12:10:57 2019 Killing 1 processes (PIDS:16174) (Process by index) in order to remove hung processes. Requested by OS process 16170 Mon Jul 01 12:12:14 2019 ARCH: krsv_hung_process_check: Error 16198 due to hung I/O operation to LOG_ARCHIVE_DEST_1 Mon Jul 01 12:13:44 2019 Thread 1 cannot allocate new log, sequence 57 Checkpoint not complete Current log# 4 seq# 56 mem# 0: /rdsdbdata/db/FAB001_A/onlinelog/o1_mf_4_gf312q1j_.log Mon Jul 01 12:14:54 2019 Thread 1 advanced to log sequence 57 (LGWR switch) Current log# 1 seq# 57 mem# 0: /rdsdbdata/db/FAB001_A/onlinelog/o1_mf_1_gf312p3q_.log Mon Jul 01 12:17:31 2019 ARC0: Detected ARCH process failure ARC0: STARTING ARCH PROCESSES Starting background process ARC1 Mon Jul 01 12:17:31 2019 ARC1 started with pid=40, OS id=10593 ARC1: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE ARC0: Becoming the 'no FAL' ARCH ARC0: Becoming the 'no SRL' ARCH Mon Jul 01 12:19:31 2019 Thread 1 cannot allocate new log, sequence 58 Checkpoint not complete Current log# 1 seq# 57 mem# 0: /rdsdbdata/db/FAB001_A/onlinelog/o1_mf_1_gf312p3q_.log Mon Jul 01 12:21:04 2019 ORACLE Instance FAB001 - Cannot allocate log, archival required Mon Jul 01 12:21:04 2019 Thread 1 cannot allocate new log, sequence 58 All online logs need archiving Examine archive trace files for archiving errors Current log# 1 seq# 57 mem# 0: /rdsdbdata/db/FAB001_A/onlinelog/o1_mf_1_gf312p3q_.log Mon Jul 01 12:24:14 2019 WARN: ARCH: Terminating process hung on an operation (PID:16176) Mon Jul 01 12:25:14 2019 Killing 1 processes (PIDS:16176) (Process by index) in order to remove hung processes. Requested by OS process 16170 Mon Jul 01 12:34:14 2019 WARN: ARCH: Terminating process hung on an operation (PID:16178) Mon Jul 01 12:37:22 2019 Killing 1 processes (PIDS:16178) (Process by index) in order to remove hung processes. Requested by OS process 16170 Mon Jul 01 12:38:24 2019 ARCH: Detected ARCH process failure Mon Jul 01 12:42:24 2019 WARN: ARCH: Terminating process hung on an operation (PID:16172) Mon Jul 01 12:43:24 2019 Killing 1 processes (PIDS:16172) (Process by index) in order to remove hung processes. Requested by OS process 16170 Mon Jul 01 12:47:40 2019 Archived Log entry 16875 added for thread 1 sequence 54 ID 0x5bfbce85 dest 1: ARC1: Detected ARCH process failure ARC1: Detected ARCH process failure ARC1: STARTING ARCH PROCESSES Starting background process ARC0 Mon Jul 01 12:47:41 2019 ARC0 started with pid=25, OS id=13561 Starting background process ARC2 Mon Jul 01 12:47:41 2019 ARC2 started with pid=26, OS id=13564 Starting background process ARC3 Mon Jul 01 12:47:41 2019 ARC3 started with pid=27, OS id=13568 ARC0: Archival started ARC2: Archival started ARC3: Archival started ARC1: STARTING ARCH PROCESSES COMPLETE ARC1: Becoming the 'no FAL' ARCH ARC1: Becoming the 'no SRL' ARCH Mon Jul 01 12:47:41 2019 ARC0: Becoming the heartbeat ARCH Using STANDBY_ARCHIVE_DEST parameter default value as /rdsdbdata/db/FAB001_A/arch/redolog Mon Jul 01 12:47:44 2019 Thread 1 advanced to log sequence 58 (LGWR switch) Current log# 2 seq# 58 mem# 0: /rdsdbdata/db/FAB001_A/onlinelog/o1_mf_2_gf312pf4_.log Mon Jul 01 12:52:51 2019 Thread 1 cannot allocate new log, sequence 59 Checkpoint not complete Current log# 2 seq# 58 mem# 0: /rdsdbdata/db/FAB001_A/onlinelog/o1_mf_2_gf312pf4_.log Mon Jul 01 12:54:38 2019 ORACLE Instance FAB001 - Cannot allocate log, archival required Mon Jul 01 12:54:38 2019 Thread 1 cannot allocate new log, sequence 59 All online logs need archiving Examine archive trace files for archiving errors Current log# 2 seq# 58 mem# 0: /rdsdbdata/db/FAB001_A/onlinelog/o1_mf_2_gf312pf4_.log Mon Jul 01 13:00:04 2019 WARN: ARCH: Terminating process hung on an operation (PID:10593) Mon Jul 01 13:02:52 2019 Killing 1 processes (PIDS:10593) (Process by index) in order to remove hung processes. Requested by OS process 16170 Mon Jul 01 13:04:03 2019 ARCH: krsv_hung_process_check: Error 16198 due to hung I/O operation to LOG_ARCHIVE_DEST_1 Mon Jul 01 13:09:33 2019 WARN: ARCH: Terminating process hung on an operation (PID:13568) Mon Jul 01 13:10:33 2019 Killing 1 processes (PIDS:13568) (Process by index) in order to remove hung processes. Requested by OS process 16170 Mon Jul 01 13:12:34 2019 ARC0: Detected ARCH process failure Mon Jul 01 13:12:51 2019 ARC0: STARTING ARCH PROCESSES Starting background process ARC1 Mon Jul 01 13:12:51 2019 ARC2: Becoming the 'no FAL' ARCH ARC2: Becoming the 'no SRL' ARCH Mon Jul 01 13:12:51 2019 ARC1 started with pid=24, OS id=16168 Mon Jul 01 13:12:51 2019 ARC1: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Mon Jul 01 13:22:08 2019 ARC2: Detected ARCH process failure ARC2: STARTING ARCH PROCESSES Starting background process ARC3 Mon Jul 01 13:22:08 2019 ARC3 started with pid=27, OS id=17139 ARC3: Archival started ARC2: STARTING ARCH PROCESSES COMPLETE Mon Jul 01 13:24:33 2019 Archived Log entry 16876 added for thread 1 sequence 55 ID 0x5bfbce85 dest 1: Mon Jul 01 13:24:33 2019 Archived Log entry 16877 added for thread 1 sequence 56 ID 0x5bfbce85 dest 1: krse_arc_driver_core: Successful archiving of previously failed ORL ``` Is there a limitation on **file size** or **the amount of time** this operation is allowed to consume? The log file indicates that something about **archiving of log files** is going wrong. Is it possible to deactivate those processes temporarily or is it just something else that is going to fail then? _Please advice! Thank you._ Best Regards, sl Edited by: sl-aws-forums on Jul 2, 2019 8:30 AM
1
answers
0
votes
0
views
asked 3 years ago
  • 1
  • 90 / page