nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GetNextID widget

Diwakara_Rao_Matha

Hi,

We are using GetNextID widget for one of the attribute which is a primary key, in dev the total number of records generated by GetNextID is 90.

We exported the CI's to stage environement so the total number of records in stage is 90 when i try creating a new ci which has GetNextID widget it is throwing oracle ERROR "Unique Constraint" becasue GetNextID is again starting the sequence from 1

Generally when i create a new CI it has to start from 91 instead of 1.

Please help me in fixing the issue.

Thanks,

Diwakar

Find more posts tagged with

Comments

Robert_Kraai

Update the table manually to set the next I'd to 91.

On Sep 19, 2012, at 1:45 AM, "eLink Entry: Discussion Group - Web Experience Management" <v7webcontentmanagement@elinkkc.opentext.com> wrote:

eLink : GetNextID widget
GetNextID widget Posted bydiwakararaom@virtusa.com (Rao Matha, Diwakara)On 09-19-2012 02:40

Hi, We are using GetNextID widget for one of the attribute which is a primary key, in dev the total number of records generated by GetNextID is 90. We exported the CI's to stage environement so the total number of records in stage is 90 when i try creating a new ci which has GetNextID widget it is throwing oracle ERROR "Unique Constraint" becasue GetNextID is again starting the sequence from 1 Generally when i create a new CI it has to start from 91 instead of 1. Please help me in fixing the issue. Thanks, Diwakar
[To post a comment, use the normal reply function]
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center

Vijay_Agrawal

Hi Diwakar,

Update the table vgnASNextID. Run the following SQL query to fix this issue:

Update VgnASNextID set NEXTID=91 where NEXTIDKEY=’<Column_name_of_GetNextID>;

Vijay Agrawal

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, September 19, 2012 1:46 AM
To: eLink Recipient
Subject: GetNextID widget

GetNextID widget

Posted by diwakararaom@virtusa.com (Rao Matha, Diwakara) On 09-19-2012 02:40

Hi,

We are using GetNextID widget for one of the attribute which is a primary key, in dev the total number of records generated by GetNextID is 90.

Generally when i create a new CI it has to start from 91 instead of 1.

Please help me in fixing the issue.

Thanks,

Diwakar

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Diwakara_Rao_Matha

Hi Vijay,

Thanks for your reply,

I updated the DB manually it worked fine

I imported the content to dev 8.1 from 7.6 but at that time i dint get any issues with GetNextID,but i dont know why it came on stage, how to avoid the occurence of this issue in prod

Thanks,

Diwakar

Vijay_Agrawal

Hi Diwakar,

This issue is normally seen when you do import/export of contents. Somehow the GetASNextID table is not updated. I have no idea how you can avoid this .

I do not think there is any fixed solution for this (apart from updating the table). Try running the same query on prod (if you face the same issue) as well to fix this.

All the best for your content move on prod

-Vijay

Diwakara_Rao_Matha

HI Vijay,

Thanks for the information

Thanks,

Diwakar

David_Stiles

The best approach for avoiding these conflicts is to define a range of id values for each WEM instance. The column that you’ve now updated to correct the immediate problem can be initialized to the first value you want to use. By setting this value differently, and with a sufficient range, on each WEM instance, you can avoid conflicts when creating new instances. More detail and discussion is covered in the following KB article:

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17533691&objAction=ArticleView

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, September 19, 2012 4:45 AM
To: eLink Recipient
Subject: RE GetNextID widget

RE GetNextID widget

Posted bydiwakararaom@virtusa.com (Rao Matha, Diwakara) On 09-19-2012 05:38

HI Vijay,

Thanks for the information

Thanks,

Diwakar

[To post a comment, use the normal reply function]
Topic:	GetNextID widget
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Robert_Kraai

On that note, the import never touches that table, and there is no export of that table’s information. To “fix” this issue, Open Text would have to add a new export command to explicitly export and import the nextID information with the content instance. The program cannot assume that you want to update the nextid table because the set of data might not be inclusive of enough data to require the nextid table to be updated.

You CAN get around that issue by using GUIDs instead of the Next ID on the content instance. Then you don’t experience problems with new primary keys or with exporting and importing across different systems. GUIDs are by definition universally unique. If you are doing a lot of exporting and importing across systems, then you need to go that direction or plan to manually update the nextid table every time.

---Bob

Robert Kraai

ApplicationONE, Inc.

(913) 707-2019

rkraai@aci1.com

www.aci1.com

The information in this email is confidential and may be legally priviledged. If you are not the intended recipient, you may not read, use or disseminate the information.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, September 19, 2012 4:16 AM
To: eLink Recipient
Subject: RE GetNextID widget

RE GetNextID widget

Posted by vijay.agrawal@hrblock.com (Agrawal, Vijay) On 09-19-2012 05:09

Hi Diwakar,

This issue is normally seen when you do import/export of contents. Somehow the GetASNextID table is not updated. I have no idea how you can avoid this .

I do not think there is any fixed solution for this (apart from updating the table). Try running the same query on prod (if you face the same issue) as well to fix this.

All the best for your content move on prod

-Vijay

[To post a comment, use the normal reply function]
Topic:	GetNextID widget
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Robert_Kraai

Well, in this case, he’s upgrading, so there isn’t a benefit to that for him.

As a strategy for managing ranges on different systems as you mentioned below, then you lose integrity between the systems. That might be ok, and certainly, if you delete all content on something like a Dev server before reimporting Prod, and the nextID is set outside the prod range, then importing and moving forward works.

But I still prefer the GUID to avoid any conflict altogether.

Robert Kraai

ApplicationONE, Inc.

(913) 707-2019

rkraai@aci1.com

www.aci1.com

The information in this email is confidential and may be legally priviledged. If you are not the intended recipient, you may not read, use or disseminate the information.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, September 19, 2012 9:21 AM
To: eLink Recipient
Subject: RE RE GetNextID widget

RE RE GetNextID widget

Posted by dstiles@opentext.com (Stiles, David) On 09-19-2012 10:20

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17533691&objAction=ArticleView

RE GetNextID widget

Posted by diwakararaom@virtusa.com (Rao Matha, Diwakara) On 09-19-2012 05:38

HI Vijay,

Thanks for the information

Thanks,

Diwakar

[To post a comment, use the normal reply function]
Topic:	GetNextID widget
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	GetNextID widget
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

David_Stiles

Sure, if it’s a onetime occurrence then the range approach has little value. But there was also a question of how to avoid future encounters.

I’m not sure how this approach causes any loss of integrity though. It doesn’t matter what the values of the ids are and the only need is to ensure they are unique. Defining ranges simply helps to ensure uniqueness across those multiple systems as new content items get created on different systems. One thing you certainly want to avoid in an environment where content is being shared/migrated across multiple systems is creating an item on one system and another item on a different system and having the two of them end up with the same id, then you *would* have a loss of integrity. But the range approach I suggest avoids this too.

One thing I do agree with is that using GUIDs is far better than any of this, and that’s a suggestion also made in the KB I pointed to.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, September 19, 2012 10:19 AM
To: eLink Recipient
Subject: RE RE RE GetNextID widget

RE RE RE GetNextID widget

Posted byrkraai@aci1.com (Kraai, Robert) On 09-19-2012 11:17

Well, in this case, he’s upgrading, so there isn’t a benefit to that for him.

But I still prefer the GUID to avoid any conflict altogether.

Robert Kraai

ApplicationONE, Inc.

(913) 707-2019

rkraai@aci1.com

www.aci1.com

The information in this email is confidential and may be legally priviledged. If you are not the ! intended recipient, you may not read, use or disseminate the information.

RE RE GetNextID widget

Posted by dstiles@opentext.com (Stiles, David) On 09-19-2012 10:20

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17533691&objAction=ArticleView

RE GetNextID widget

Posted by diwakararaom@virtusa.com (Rao Matha, Diwakara) On 09-19-2012 05:38

HI Vijay,

Thanks for the information

Thanks,

Diwakar

[To post a comment, use the normal reply function]
Topic:	GetNextID widget
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

[To post a comment, use th! e normal reply function]
Topic:	GetNextID widget
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	GetNextID widget
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center