tag:blogger.com,1999:blog-6850817271941197798.post6728691064997243267..comments2011-12-27T10:20:33.163-08:00Satishbabu Gunukulahttp://www.blogger.com/profile/02630966486825083489noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-6850817271941197798.post-26612409722538881442011-12-27T10:20:33.163-08:002011-12-27T10:20:33.163-08:00Hi Niranjan,<br /><br />Please see the below posts<br />http://www.oracleracexpert.com/2009/10/cross-platform-transportable-tablespace.html<br />http://www.oracleracexpert.com/2009/08/transportable-tablespace-export-import.html<br /><br />Regards<br />Satishbabu GunukulaSatishbabu Gunukulahttp://www.blogger.com/profile/02630966486825083489noreply@blogger.comtag:blogger.com,1999:blog-6850817271941197798.post-47968095963862345422011-12-24T07:26:55.842-08:002011-12-24T07:26:55.842-08:00hi satish,<br /><br />Please send me how to migrate database from DB2 to Oracle 10.2g or 11gNiranjanhttp://www.blogger.com/profile/05949700613882462904noreply@blogger.comtag:blogger.com,1999:blog-6850817271941197798.post-7304769014897671002009-09-08T15:29:00.589-07:002009-09-08T15:29:00.589-07:00Hi,<br /><br />This error indicates that the SGA is large for the amount of shared memory you have allocated in kernel configuration file.<br /><br />See the below post and try workaround 1 and 2 <br />http://oracleracexpert.blogspot.com/2009/08/ora-27102-out-of-memory-on-solaris.html<br /><br />The same issue has been resolved for many clients with this workaround.<br /><br />Regards,<br />Satishbabu GunukulaSatishbabu Gunukulahttp://www.blogger.com/profile/02630966486825083489noreply@blogger.comtag:blogger.com,1999:blog-6850817271941197798.post-17547449040746537852009-09-07T09:47:22.831-07:002009-09-07T09:47:22.831-07:00Hello Satishbabu Gunukula, thanks for your answer.<br /><br />The database(10g R2)have 1168M in sga_max_size, so I tried to increase it to 2000M because the server have 4GB of physical memory, and in the moment of startup appear this error.<br /><br />Yes, I read all your posts about this errors and I have checked all the kernel parameters. Now I change the shmall to shmmax/page_size, in spite of this change the database don´t start.<br /><br />If you need more information about the situation, please tell me.<br /><br />Thanks.Facundohttp://www.blogger.com/profile/04639472341633907785noreply@blogger.comtag:blogger.com,1999:blog-6850817271941197798.post-40308347605663138372009-09-03T16:45:17.848-07:002009-09-03T16:45:17.848-07:00Hi,<br /><br />What are you doing, when you received ORA-27102 error? <br /><br />Did you see all my posts on this error? Did you try the workaround?<br /><br />See the posts under &quot;Ora-Errors&quot; category.<br /><br />Regards,<br />Satishbabu GunukulaSatishbabu Gunukulahttp://www.blogger.com/profile/02630966486825083489noreply@blogger.comtag:blogger.com,1999:blog-6850817271941197798.post-77781040640627722202009-08-31T13:05:04.336-07:002009-08-31T13:05:04.336-07:00Hello, I have the same error but in a SUSE Linux Enterprise Server 10 (i586) with 32 bits.<br /><br />The kernel parameters are:<br /><br />kernel.shmall = 268435200<br />kernel.shmmax = 4294967295<br /><br />and the kernel version is:<br /><br />Linux db-r2-01 2.6.16.46-0.12-bigsmp #1 SMP Thu May 17 14:00:09 UTC 2007 i686 i686 i386 GNU/Linux<br /><br />If this error appear RedHat it would be fix updating the kernel to hugemem version as explain the DOC ID 746178.1 of Metalink. But in Suse I haven´t idea.<br /><br />Any suggestion? Thanks.Facundohttp://www.blogger.com/profile/04639472341633907785noreply@blogger.com