Skip to main content
NetApp Knowledge Base

SCO clone fails due to low sga_target memory allocation

  1. Last updated
  2. Save as PDF
Views:
13
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter Plug-in for Oracle [SCO]
  • Oracle SGA [System Global Area]

Issue

SCO database clone attempt fails with:
 

spl_JobID.date_xxxxxx_xxxx.log

2025-01-16T19:55:53.0000448ZDEBUG qtp608686137-6671 c.n.o.c.s.d.DatabaseConfigurationService - failed tocomplete method startDatabaseWithpFile  with JVM free memory 968.3 MB andused memory 1.1 GB.
2025-01-16T19:55:53.0000448Z ERROR qtp608686137-6671c.n.o.c.s.d.DatabaseConfigurationService - An exception thrown during theexecution of method startDatabaseWithpFile and the exception message isORACLE-00001: Errorexecuting SQL: [STARTUP NOMOUNT EXCLUSIVEPFILE=/opt/oracle/finsig/product/64bit/19.0.0/dbs/initfinsig2.ora;].  Thecommand returned: ORA-32006: SEC_CASE_SENSITIVE_LOGON initialization parameterhas been deprecated
ORA-00821: Specified value of sga_target 2048M is too small, needs to be atleast 6496M
ORA-01078: failure in processing system parameters.
 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.