Solved

Database Copy error

  • 1 December 2020
  • 6 replies
  • 364 views
M
Rank
Userlevel 5
Badge +10

Hi,

 

We have recently copied our database, App9 first time in Oracle 19 and had an error message.

 

Before we go down Support route has anyone else had this error message:

 

ORA-04031: unable to allocate 48 bytes of shared memory ("shared pool","select /*+ rule */ bucket_cn...","SQLA^f5f698ce","idndef : qcuAllocIdn")
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2020-11-30T09:50:39.145808+00:00
Errors in file C:\APP\ORACLE\diag\rdbms\ifscst\ifscst\trace\ifscst_j006_5824.trc  (incident=296980):
ORA-04031: unable to allocate 40 bytes of shared memory ("shared pool","select audit$ from tab$ wher...","SQLA","tmp")
2020-11-30T09:50:39.145808+00:00
Errors in file C:\APP\ORACLE\diag\rdbms\ifscst\ifscst\trace\ifscst_j008_4428.trc  (incident=297005):
ORA-04031: unable to allocate 48 bytes of shared memory ("shared pool","select /*+ rule */ bucket_cn...","SQLA^f5f698ce","idndef : qcuAllocIdn")
ORA-04031: unable to allocate 272 bytes of shared memory ("shared pool","select name,online$,contents...","SQLA^ce517e03","kccdef: qkxrMemAlloc")
ORA-06512: at "IFSAPP.DATABASE_SYS", line 1441
ORA-06512: at "IFSAPP.DATABASE_SYS", line 13
ORA-06512: at "IFSAPP.DICTIONARY_SYS", line 1889
ORA-06512: at "IFSAPP.DICTIONARY_SYS", line 167
ORA-06512: at "IFSAPP.DOMAIN_SYS", line 679
ORA-06512: at "IFSAPP.DOMAIN_SYS", line 150
ORA-06512: at "IFSAPP.FND_BOOLEAN_API", line 419
ORA-06512: at "IFSAPP.FND_BOOLEAN_API", line 423
ORA-06512: at "IFSAPP.FND_BOOLEAN_API", line 427
ORA-06512: at "IFSAPP.DOMAIN_SYS", line 678
ORA-06512: at "IFSAPP.DOMAIN_SYS", line 150
ORA-06512: at "IFSAPP.LOG_CATEGORY_API", line 348
ORA-06512: at "IFSAPP.LOG_CATEGORY_API", line 352
ORA-06512: at "IFSAPP.LOG_CATEGORY_API", line 356
ORA-06512: at "IFSAPP.LOG_SYS", line 65
ORA-06512: at "IFSAPP.TRACE_S

Thanks in advance,

 

Matthew

icon

Best answer by durette 2 December 2020, 23:47

View original
This topic has been closed for comments

6 replies

Srikanth
Rank
Userlevel 6
Badge +18

Looks like the DB Server hosting your cloned instance doesn’t have enough RAM to allocate.  

Can you please check if this is the case?

Cheers, Srikanth
M
Rank
Userlevel 5
Badge +10

I shall look.

 

We have run databases on here before that is what is surprising. Anyone know of any recent changes that would lead to not enough RAM?

M
Rank
Userlevel 5
Badge +10

The server has 48G RAM. There are 4 databases each with 10G allocated. So this leaves 8G for the OS. It is a little tight on free memory but not critical.”

durette
Rank
Userlevel 7
Badge +18

It looks like you need to increase your shared pool size. The way to do this depends on whether you’re using Automatic Memory Management, Automatic Shared Memory Management, or manual memory management.

What are the values of each of these parameters?

  • shared_pool_size
  • sga_target
  • sga_max_size
  • memory_target
  • memory_max_target
  • pga_aggregate_target
  • pga_aggregate_limit
If you find this forum useful, please consider paying back to the community in your own areas of expertise. -- Kevin Durette - https://www.linkedin.com/in/kevindurette
M
Rank
Userlevel 5
Badge +10

Hi,

 

Thanks - yes our DB Support Partners finally got to the bottom of it - was related to memory management.

 

 

durette
Rank
Userlevel 7
Badge +18

Ironically, I hit this today while running a script, in case anyone is searching for this issue.

ORA-04031: unable to allocate 104 bytes of shared memory ("shared pool" ...

I normally put this in my SQL*Plus scripts:

SET AUTOTRACE ON

This issue went away when I disabled autotrace.

SET AUTOTRACE OFF

 

If you find this forum useful, please consider paying back to the community in your own areas of expertise. -- Kevin Durette - https://www.linkedin.com/in/kevindurette
Terms & ConditionsCookie settings