on 10-03-2011 2:16 PM
Hi,
we are in QA now.
We have done some data migration activity in QA.
and the ID field (AutoID) has reached 1743 in QA.
When Movement to production, i will be deleting all the records in QA.
Take an Archive and Unarchive it Production.
In Prod we perform a actual Data migration.
But when i do this the ID will increment from 1743 and not from 1.
How to reset it to 1 when loading freshly , after deleting Old records.
Also are there any Precautions/ Basic Actions needs to be performed or kept in Mind during making thngs LIVE!!!
KR
John
Hi John,
You can use one of the following option to ensure that Auto ID in Production starts with 1.
1. Take Schema only archive and unarchive in Production.
2. Delete Auto ID fielda and recreate. Ensure to backup all the field details before deleting. - I have already tried this and it works.
3. Reset directly in Database.
Production checks:
1. All Repository level configurations. e.g. Remote Systems, Ports, Number Ranges. workflows, assigments, validations etc.
2. All *.ini file settings. Includes archive, distribution directory settings etc.
3. Connectivity check with MDM if you have Portal / PI or any other component in your landscape.
Hope this helps.
Best Regards,
Amol.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
As suggested in the other posts you can reset/recreate MDMID field.
Just curious,any particular reason you wish to keep it that way,a business reason or some thing?
Coming to 2nd part of your question-
-> Make sure data is not lost and data count is same between systems.All the exceptions have been handled.
->Review that roles and privileges are proper as this is one area which gives recurring issue post go-live
->Take special care if you are using multiple main table of syndication maps with property "Suppress unchanged record - SET",unknowingly data can get syndicated this way.
->Review your configurations i.e.Maps,Portal screens,privileges to users in WF/Screens/table level/functionality level etc.
->Also make sure all the environments are in sync,this can really save the day for you when you wish to replicate an issue and troubleshoot apart from other reasons.In your case post MDMID change the same should be replicated to other environments.
and yes, All the best
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
You can use one of the following option to ensure that Auto ID in Production starts with 1.
1. Take Schema only archive and unarchive in Production.
2. Delete Auto ID fielda and recreate. Ensure to backup all the field details before deleting. - I have already tried this and it works.
3. Reset directly in Database.
Production checks:
1. All Repository level configurations. e.g. Remote Systems, Ports, Number Ranges. workflows, assigments, validations etc.
2. All *.ini file settings. Includes archive, distribution directory settings etc.
3. Connectivity check with MDM if you have Portal / PI or any other component in your landscape.
Hope this helps.
Best Regards,
Amol.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
I am not quite sure so just try this out.. Please delete firstly this Auto ID field and then re-create a new Auto-ID field. May be in this way you could have Auto-ID counter restarts from 1.
Otherwise From Database, you can reset this Auto-ID counter from 1.
Kindly revert with findings.
Regards,
Mandeep Saini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.