Database Error 8102
Administrator Previous post Next post Currently Being Moderated Database error 8102 during client copy Posted by Pradeep Kotikalapudi in SAP NetWeaver Administrator on Mar 28, 2012 5:48:15 AM Tweet Hi All,I am from Basis team and this is my first blog to SCN. I want to share my experience while performing a local client copy.I was doing a client copy on Unix- Oracle environment and we ran into error "Database error 8102". The exact error log from SM21 is below,Error: (from sm21)Database error 8102 at DEL access to table ACCTHD> ORA-08102: index key not found, obj# 31189, file 34, block> 1200035 (2)The error clearly shows that index key was not found for an object in the table. Index for the tables mentioned in the error (ACCTHD) in the above case were corrupted. Hence DB action DEL(delete) is failing on these tables. I have checked several forums with the error code ORA-8102 and in most of them suggested to rebuild the index for all tables.Luckily we have an experienced Oracle DBA in our project and with his help we were able to solve this by rebuilding Index for the table corrupted.Below are steps to rebuild the Index,Step #1 : Logon to your server as ORA
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries Inside-ERP MacProTX VoIP_News Inside-CRM PCMag I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker JoeTorre bracke Locutus Ramnath.Awate Richard DukeGanote Craig Borysowich Dennis Stevenson Nikki Klein mircea_luca AbhaiTripathi knowscognosdoi Clinton Jones bluesguyAZ59 Iqbalyk http://scn.sap.com/community/netweaver-administrator/blog/2012/03/28/database-error-8102-during-client-copy blrvenkat COMPANIES Juniper Networks CloudLock Avaya Adaptive Planning View All Topics View All Members View All Companies Toolbox for IT Topics SAP Groups Ask a New Question SAP Basis The SAP Basis group is for the discussion of specific configuration and development issues that arise when utilizing the SAP Basis & System Administration. Home | Invite Peers | More SAP Groups Your http://sap.ittoolbox.com/groups/technical-functional/sap-basis/after-restore-database-getting-dump-in-st22-5808800 account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. After Restore Database Getting Dump In St22 Satish Ahirkar asked Sep 25, 2015 | Replies (3) Dear All, I restore the Oracle database and upgrade oracle 11.0.2 to 11.0.3, I have getting error below in ST22. Please guide me. Category Installation Errors Runtime Errors DBIF_RSQL_SQL_ERROR Except. CX_SY_OPEN_SQL_DB Date and Time 25.09.2015 10:06:09 Short text SQL error 8102 when accessing table "TBTCO". What happened? Error Text of the Database: "ORA-08102: index key not found, obj# 94860, file 12, block 270447 (2)" Error analysis An exception occurred that is explained in detail below. The ex
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack http://dba.stackexchange.com/questions/106817/how-do-i-prevent-an-ora-08102-error Overflow the company Business Learn more about hiring developers or posting ads with us http://www.dbforums.com/showthread.php?779346-error-8102-cannot-update-identity-column Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can database error answer The best answers are voted up and rise to the top How do I prevent an ORA-08102 error up vote 0 down vote favorite I am getting an ORA error (08102 - Index Key Not Found) with several customers, and I have been unable to reproduce or explain it. They have all been on the same index on the same table. This error is tied to two tables - ALPHA and database error 8102 BRAVO. ALPHA has a primary key on alpha_id. BRAVO links to ALPHA by a foreign key reference to ALPHA.alpha_id. For these customers, all BRAVO rows point to a single APLHA row on the BRAVO table. We have an index on the BRAVO table whose only column is BRAVO.alpha_id. That index, ALPHA_ID_FK, is generating the error when we go to delete rows. As I said, I have been unable to replicate this myself, but I'm getting reports of the same problem by several different customers. We are sometimes able to rebuild the index to correct this issue, but even rebuilding the index is not working for all customers. What is causing this error, and how can I better prevent it? oracle oracle-11g-r2 errors share|improve this question asked Jul 13 '15 at 21:41 rStyskel 1112 Have you contacted Oracle support? The fact that you're getting corrupted index structures often enough to have solutions that work "sometimes" and to be looking to prevent it implies that you have an underlying problem that needs to be diagnosed. You could try dropping and recreating the index rather than just rebuilding it. You could try rebuilding the table and then rebuilding the indexes. But I'd definitely get a support ticket opened with the trace file(s) you're getting. &n
your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 12 of 12 Thread: error 8102:cannot update identity column Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 05-09-03,09:35 #1 cobraeyez View Profile View Forum Posts Registered User Join Date May 2003 Posts 11 Unanswered: error 8102:cannot update identity column HI I have 2 SQL Servers 2000 enterprise version. I setup a transactional replication between them. There is a table using identity feature and set to not for replication. On the server A as publication, B as Subscriber. I created table in B manually and set the name conflict in article default to keep existing data. When it replicates at the first time, everything is fine, but if there is some data added to the table in Server A, the replication fails, saying cannot update indentity column. I read about something on add Set Identity on/off thing. But I dont know which SP I should add this to. Please help. As detail as possible. Thanks. Reply With Quote 05-09-03,12:51 #2 JohnB020 View Profile View Forum Posts Visit Homepage Registered User Join Date May 2003 Location California Posts 7 Bug WorkAround There is a bug in the Managed Range Identity system. In Merge Replication I have found that while creating a publication using range identities it will work only the first time. Changing settings such as Publisher range or subscriber range does not have an effect. Also, deleting the subscriptions and publications DOES NOT remove the constraints from the affected subscriber tables. Also, the entry for the database in the replication distribution DB table MSrepl_identity_range does not get deleted and therefore the next time the publication is run it will not take the correct settings. In order to successfully recreate the subscription you must delete the row(s) from the afore mentioned table and remove all constraints manually. Only then will it work. If the constraints are not removed the