Problem Note 48337: Exporting an information map that is based on a cube might fail because of insufficient memory
If you try to export a SAS
® Information Map into a SAS package file in SAS
® Management Console, the export might fail with the following exception in the export log:
ERROR - The Information Map "tab1" had an error loading dependencies.
com.sas.iquery.metadata.MetadataException: An error occurred while retrieving metadata.
at com.sas.iquery.metadata.business.impl.ReadingContextV2.finishExternalResourceResolution(ReadingContextV2.java:767)
at com.sas.iquery.metadata.business.impl.ReadingContextV2.replaceExternalResourcesWithinModel(ReadingContextV2.java:724)
at com.sas.iquery.metadata.business.impl.AbstractBusinessModel.postPopulationProcessing(AbstractBusinessModel.java:2555)
at com.sas.iquery.metadata.business.impl.AbstractModel.doPostProcessing(AbstractModel.java:2121)
at com.sas.iquery.metadata.business.impl.AbstractModel.pushXMLAndPostProcess(AbstractModel.java:2099)
at com.sas.iquery.metadata.business.impl.InformationMapImpl.readSAXV2(InformationMapImpl.java:2379)
at com.sas.iquery.metadata.business.impl.InformationMapImpl.readV2(InformationMapImpl.java:2326)
at com.sas.iquery.metadata.business.impl.InformationMapImpl.readInNewMap(InformationMapImpl.java:2199)
at com.sas.iquery.metadata.business.impl.InformationMapImpl.fetchMap(InformationMapImpl.java:4002)
at com.sas.iquery.metadata.business.impl.InformationMapImpl.readInNewMap(InformationMapImpl.java:2016)
at com.sas.iquery.metadata.resourceutil.InformationMapResourceReplacementManager.≤init≥(InformationMapResourceReplacementManager.java:203)
at com.sas.iquery.metadata.resourceutil.InformationMapResourceReplacementManager.≤init≥(InformationMapResourceReplacementManager.java:160)
at com.sas.metadata.logical.informationmap.InformationMapExportListener.getPhysicalResourceTreeForMap(InformationMapExportListener.java:215)
at com.sas.metadata.logical.informationmap.InformationMapExportListener.createPhysicalResourceTreeForMaps(InformationMapExportListener.java:157)
at com.sas.metadata.logical.informationmap.InformationMapExportListener.analyzeConnections(InformationMapExportListener.java:99)
at com.sas.metadata.promotion.ExportHandler.analyzeConnections(ExportHandler.java:631)
at com.sas.metadata.promotion.ExportHandler.runExport(ExportHandler.java:522)
at com.sas.metadata.promotion.visuals.ExportExecutePanel$ExportThread.launchOperation(ExportExecutePanel.java:71)
at com.sas.metadata.promotion.visuals.AbstractExecutePanel$ExecutionThread.run(AbstractExecutePanel.java:442)
Caused by: com.sas.services.ServiceException: An error occurred while retrieving metadata. [ com.sas.metadata.remote.MdException: Insufficient memory [ org.omg.CORBA.NO_MEMORY: Insufficient memory ] ]
at com.sas.iquery.metadata.business.impl.V2ResourceResolver.resolveResources(V2ResourceResolver.java:286)
at com.sas.iquery.metadata.business.impl.V2ResourceResolver.run(V2ResourceResolver.java:218)
at com.sas.iquery.metadata.business.impl.thread.WorkerThread.doCurrentWorkNow(WorkerThread.java:168)
at com.sas.iquery.metadata.business.impl.thread.WorkerThread.run(WorkerThread.java:262)
Caused by: com.sas.services.ServiceException: An error occurred while retrieving metadata. [ com.sas.metadata.remote.MdException: Insufficient memory [ org.omg.CORBA.NO_MEMORY: Insufficient memory ] ]
at com.sas.services.information.OMIServer.doSearch(OMIServer.java:5859)
at com.sas.services.information.OMIServer.search(OMIServer.java:5773)
at com.sas.iquery.metadata.impl.IQModelImplUtilities.generalSearch(IQModelImplUtilities.java:2600)
at com.sas.iquery.metadata.business.impl.V2ResourceResolver.runQueriesToGetOmrObjects(V2ResourceResolver.java:2609)
at com.sas.iquery.metadata.business.impl.V2ResourceResolver.locateAndBindMetadataRepositoryResources(V2ResourceResolver.java:716)
at com.sas.iquery.metadata.business.impl.V2ResourceResolver.resolveResources(V2ResourceResolver.java:271)
... 3 more
Caused by: com.sas.metadata.remote.MdException: Insufficient memory
at com.sas.metadata.remote.MdOMIWrapperImpl.getMetadataObjectsFromServer(MdOMIWrapperImpl.java:1754)
at com.sas.metadata.remote.MdOMIWrapperImpl.getMetadataObjectsSubset(MdOMIWrapperImpl.java:675)
at com.sas.metadata.remote.MdOMIUtilImpl.getMetadataObjectsSubset(MdOMIUtilImpl.java:1799)
at com.sas.metadata.remote.MdOMIUtilImpl.getMetadataObjectsSubset(MdOMIUtilImpl.java:1781)
at com.sas.services.information.OMIServer.doSearch(OMIServer.java:5820)
... 8 more
Caused by: org.omg.CORBA.NO_MEMORY: Insufficient memory vmcid: 0x0 minor code: 0 completed: No
at com.sas.iom.orb.brg.Engine.parseErrorXML(Engine.java:2068)
at com.sas.iom.orb.brg.Engine.checkForErrorPacket(Engine.java:1958)
at com.sas.iom.orb.brg.Engine.waitForReply(Engine.java:1924)
at com.sas.iom.orb.brg.Engine.sendRequest(Engine.java:832)
at com.sas.iom.orb.brg.RequestImpl.invoke(RequestImpl.java:37)
at com.sas.meta.SASOMI._portable_stub_IOMI.GetMetadataObjects(_portable_stub_IOMI.java:94)
at com.sas.metadata.remote.MdOMIWrapperImpl.getMetadataObjectsFromServer(MdOMIWrapperImpl.java:1750)
. . .12 additional message lines. . .
ERROR - An error occurred during the export process. Reason: java.lang.NullPointerException
INFO - The export process has finished with errors.
The problem occurs when the SAS Information Map is based on a cube, and that cube has shared dimensions associated with it. One of the queries submitted to the SAS
® Metadata Server results in multiple requests for the same cube and dimension information. This action inflates the result and causes the SAS Metadata Server to run out of memory.
The only workaround is to modify the cube definition to use only private dimensions.
Operating System and Release Information
| SAS System | SAS Management Console | Microsoft® Windows® for x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Microsoft Windows Server 2008 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Microsoft Windows XP Professional | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Enterprise 32 bit | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Enterprise x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Home Premium 32 bit | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Home Premium x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Professional 32 bit | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Professional x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Ultimate 32 bit | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows 7 Ultimate x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows Vista | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Windows Vista for x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| 64-bit Enabled AIX | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| 64-bit Enabled HP-UX | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| 64-bit Enabled Solaris | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| HP-UX IPF | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Linux | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Linux for x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
| Solaris for x64 | 9.3_M1 | 9.4 | 9.3 TS1M1 | 9.4 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
A query in the export process returns duplicate metadata that increases the size of the result, which causes the SAS® Metadata Server to exhaust all available memory.
| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Data Sources ==> Cubes
Data Management ==> Data Sources ==> Information map
System Administration ==> Servers ==> Metadata
|
| Date Modified: | 2013-04-15 17:17:35 |
| Date Created: | 2012-10-31 11:49:42 |
