Error when i set primary key to a field in table

I created a table. with one primary key field
on saving it following error happened
at Microsoft.SqlServer.Management.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDataDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)
then i removed primary key. Table was saved successfully.
I need to make primary key field.. how can i solve it?

CREATE TABLE tblname (c INT NOT NULL PRIMARY KEY)
Have you ran the above statement successfully? Do you create a table in VS?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Similar Messages

How to set primary key for a date column

hello experts .,
i need to set primary key for a column consists of the datatype date. how to solve this..?

1008318 wrote:
its my personal need..then it is a very bad personal need. DATE is not an appropriate type to be using for a primary key, as it cannot be guaranteed to be unique, especially when inserting multiple rows at once.
You would be better working to business needs and implementing correct technical solutions to those needs, than to just do things based on your personal needs.

Anyone know setting primary key deferred help in the bulk loading

Hi,
Anyone know by setting primary key deferred help in the bulk loading in term of performance..cos i do not want to disable the index, cos when user query the existing records in the table, it will affect the search query.
Thank You...

In the Oracle 8.0 documentation when deferred constraints were introduced Oracle stated that defering testing the PK constraint until commit time was more efficient than testing each constraint at the time of insert.
I have never tested this assertion.
In order to create a deferred PK constraint the index used to support the PK must be created as non-unique.
HTH -- Mark D Powell --

How to set primary key of the VO.

I have a problem with the master detail search. The search works fine on the first search, all details can be seen fine, but in the second search I get this error.
The number of displayed records, 1, exceeds the actual number of records, 0, in view object EgoItemAdvancedSearchAM.MYACCESSOR001_MYLINK001_DetailsOrderLinesVO. Some of the displayed records may have been deleted.
Somwhere in another thread, someone had the same problem and the soultion was to set primary key of the master VO. I am not sure how to set primary key of a VO. In my case the master VO is dynamic. Is there a way I can set PK of a dynamic VO.
Any help greatly appreciated.

Hi
Thanks for your reply...
am seting the primary key to VO attribute in my controller(PR)...but its not mapping to the VO attribute..
OAAttachmentImageBean Ibean = (OAAttachmentImageBean)webBean.findChildRecursive("OpAttachments");
String[] pkvaule = {"ResAttribute15"};
Ibean.setPkColumns(pkvaule);
Regards
Harrrry

Setting primary key fields from sequence. Please advise

What is the most logical place to automatically set primary key fields from
sequence?
jdoPrestore seems to be a little late - my instance will not have id till
it's committed. I can not do it in constructor because it gets called every
time Kodo needs to construct an instance. What other options do I have for
automatic pk assignment except do it in my code (hate it)?
I wish I could use store managed OIDs but I need access to OID underlying
data
Please also see my previous message "Application Identity Extention"

I came up with following pattern:
public class OrgUnit implements InstanceCallbacks {
private long orgUnitId = -1;
private transient long tempOrgUnitId = -1;
public long getOrgUnitId() {
if (orgUnitId < 0) {
if (tempOrgUnitId < 0) {
tempOrgUnitId = JDOFactory.getNextSequenceId(getClass());
return tempOrgUnitId;
} else {
return orgUnitId;
public void jdoPreStore() {
if (!JDOHelper.isDeleted(this)) {
if (orgUnitId < 0) {
setOrgUnitId(getOrgUnitId());
I use -1 as an indicator that ID has not been assigned yet. If you use Long
instead of long it will be cleaner since we can test for null
"Alex Roytman" <[email protected]> wrote in message
news:9q27co$r35$[email protected]..
What is the most logical place to automatically set primary key fieldsfrom
sequence?
jdoPrestore seems to be a little late - my instance will not have id till
it's committed. I can not do it in constructor because it gets calledevery
time Kodo needs to construct an instance. What other options do I have for
automatic pk assignment except do it in my code (hate it)?
I wish I could use store managed OIDs but I need access to OID underlying
data
Please also see my previous message "Application Identity Extention"

Getting Compilation error when used SET or MULTISET operator on nested tabl

Dear All,
I am getting Compilation error when used SET or MULTISET operator on nested tables inside a procedure.
This is working fine in other DB installations of 10g but does not work in another 10g DB.
it says "wrong number of parameter or datatype used in SET"
Can any one suggest what went wrong here?
Thanks in advance.

Can any one suggest what went wrong here?Only if you would post the query and Oracle versions on both databases.
Besides, this forum deals with issues in Oracle product installation. So post this query in SQL PL/SQL forum for better response.

Compilation error when used SET or MULTISET operator on nested tables

Dear All,
I am getting Compilation error when used SET or MULTISET operator on nested tables inside a procedure.
This is working fine in other DB installations of 10g but does not work in another 10g DB.
it says "wrong number of parameter or datatype used in SET"
Can any one suggest what went wrong here?
Thanks in advance.

Hi,
Thanks for ur reply...
Since MULTISET and SET operators are the new additions in base 10g release for manipulation of nested tables data, I am surprised that same is working in similar 5 DBs installations with 10.2.0.1.0 version, but does not work in the sixth.
SET and MULTISET operators are used inside the PL/SQL procedure which is getting compiled in the above mentioned 5 DBs but not in sixth DB.
it gives
On line: 3112
PLS-00306: wrong number or types of arguments in call to 'SET'
Hope this clarifies the issue...

How can i set primary key after creating a table ?

hi friends
thank you for all the support you have given me . i have doubt ,can we set primary key for a column after creating the table
I have added a column named idno after creating the table . i want to set that column as primary key . i tried this
table name = address
column name = idno
ALTER TABLE ADDRESS MODIFY (idno PRIMARY KEY(idno))
,but not working
if anbody knows the solution pls reply
thanks and regards
nev

how does the other users know which is the primary key for this table?....the other user needs to execute this query...and modify the query accordingly
select aa.table_name,aa.column_name,aa.constraint_name,bb.constraint_type
from user_cons_columns aa,user_constraints bb
where aa.constraint_name = bb.constraint_name
and aa.table_name = 'TEST_EMP' and bb.constraint_type = 'P';

NULL in primary keys NOT logged to exceptions table

Problem: Inconsistent behavior when enabling constraints using the "EXCEPTIONS INTO" clause. RDBMS Version: 9.2.0.8.0 and 10.2.0.3.0
- NULL values in primary keys are NOT logged to exceptions table
- NOT NULL column constraints ARE logged to exceptions table
-- Demonstration
-- NULL values in primary keys NOT logged to exceptions table
TRUNCATE TABLE exceptions;
DROP TABLE t;
CREATE TABLE t ( x NUMBER );
INSERT INTO t VALUES ( NULL );
ALTER TABLE t
ADD ( CONSTRAINT tpk PRIMARY KEY (x) EXCEPTIONS INTO exceptions );
SELECT * FROM exceptions; -- returns no rows
-- NOT NULL column constraints logged to exceptions table
TRUNCATE TABLE exceptions;
DROP TABLE t;
CREATE TABLE t ( x NUMBER );
INSERT INTO t VALUES ( NULL );
ALTER TABLE t MODIFY ( X NOT NULL EXCEPTIONS INTO EXCEPTIONS );
SELECT * FROM exceptions; -- returns one row
I would have expected all constraint violations to be logged to exceptions. I was not able to find any documentation describing the behavior I describe above.
Can anyone tell me if this is the intended behavior and if so, where it is documented?
I would also appreciate it if others would confirm this behavior on their systems and say if it is what they expect.
Thanks.
- Doug
P.S. Apologies for the repost from an old thread, which someone else found objectionable.

I should have posted the output. Here it is.
SQL>TRUNCATE TABLE exceptions;
Table truncated.
SQL>DROP TABLE t;
Table dropped.
SQL>CREATE TABLE t ( x NUMBER );
Table created.
SQL>INSERT INTO t VALUES ( NULL );
1 row created.
SQL>ALTER TABLE t ADD ( CONSTRAINT tpk PRIMARY KEY (x) EXCEPTIONS INTO exceptions );
ALTER TABLE t ADD ( CONSTRAINT tpk PRIMARY KEY (x) EXCEPTIONS INTO exceptions )
ERROR at line 1:
ORA-01449: column contains NULL values; cannot alter to NOT NULL
SQL>SELECT * FROM exceptions;
no rows selected
SQL>
SQL>TRUNCATE TABLE exceptions;
Table truncated.
SQL>DROP TABLE t;
Table dropped.
SQL>CREATE TABLE t ( x NUMBER );
Table created.
SQL>INSERT INTO t VALUES ( NULL );
1 row created.
SQL>ALTER TABLE t MODIFY ( X NOT NULL EXCEPTIONS INTO EXCEPTIONS );
ALTER TABLE t MODIFY ( X NOT NULL EXCEPTIONS INTO EXCEPTIONS )
ERROR at line 1:
ORA-02296: cannot enable (MYSCHEMA.) - null values found
SQL>SELECT * FROM exceptions;
ROW_ID OWNER TABLE_NAME CONSTRAINT
AAAkk5AAMAAAEByAAA MYSCHEMA T T
1 row selected.
As you can see, I get the expected error message. But I only end up with a record in the exceptions table for the NOT NULL column constraint, not for the null primary key value.

Primary key constraint for index-organized tables or sorted hash cluster

We had a few tables dropped without using cascade constraints. Now when we try to recreate the table we get an error message stating that "name already used by an existing constraint". We cannot delete the constraint because it gives us an error "ORA-25188: cannot drop/disable/defer the primary key constraint for index-organized tables or sorted hash cluster" Is there some sort of way around this? What can be done to correct this problem?

What version of Oracle are you on?
And have you searched for the constraint to see what it's currently attached to?
select * from all_constraints where constraint_name = :NAME;

How to know primary key column name form a table name in sql query

Suppose I only know the table name. How to get its primary key column name from the table name?
Thanks

Views don't have primary keys though their underlying tables might. You'd need to pick apart the view to determine where it's columns are coming from.
You can select the text of the view in question from user_views.

Knowing the primary key columns of the given table

Hi,
How can I get the primary key columns of the given table?
Regards,
Sachin R.K.

You can find the constraint_name from all_constraints/user_constraints for constraint_type = 'P' (which is the primary key constraint).
And then see which columns are in for the constriant_name
in all_cons_columns/user_cons_columns view.
Below is the example
select acc.column_name from
all_cons_columns acc, all_constraints ac
where acc.constraint_name = ac.constraint_name
and acc.table_name = 'DEPT' AND acc.owner = 'SCOTT'
and ac.constraint_type = 'P'
Hope this helps
Srinivasa Medam

How add primary key constraint to already existing table with data

I want apply primary key constraint to already existing table with data
is there any command or way to do

Alternatively, assuming you want to ensure uniqueness in your primary key column you can do this:
alter table <table name> add constraint <cons name> primary key (col1,col2) exceptions into <exception_table>
If the altter table statement fails this will populate the EXCEPTIONS table with the rows that contain duplicate values for (col1,col2).
You will need to run (or get a DBA to run) a script called UTLEXCPT.SQL (which will be in the $ORACLE_HOME/rdbms/admin directory) if you don't already have an EXCEPTIONS table.
Cheers, APC

Setting primary key field value in jdoPrestore() not flushed to database ?BUG?

Hello,
When I set value of primary key field of a new instance in jdoPrestore() new
value does not get flushed to database - old (default) value get stored
instead. All other fields assigned in jdoPrestore() get successfully
flushed except primary key one.
Alex

Abe,
You fixed only part of the problem. Right now if I assign value to a PK
field in jdoPreStore() it does get flushed but there is another issue - all
other instances which referenced the one I assigned PK to will not get this
PK value. Example A references B, in B.jdoPreStore() I generate id for B -
b.id = 100. When A gets flushed it would not get 100 in its b_id field.
Specs says:
This method is called ***before the values are stored from the instance to
the StateManager***.
Data store fields that might have been affected by modified non-persistent
fields should
be updated in this method. This method is modified by the enhancer so that
changes to
persistent fields will be reflected in the data store.
The context in which this call is made allows access to the
PersistenceManager and
other persistent JDO instances.
I read it as callbacks should be invoked on ALL instances before they get
stored to StateManager. Does Kodo invoke callbacks for all istances first
and then store them to instance manager? Based on the problem I am having it
does not look like it
Alex
"Abe White" <[email protected]> wrote in message
news:[email protected]..
I just confirmed this as a bug and fixed it. We should be able to post
the new jars for you soon. Hang in there.

Setting primary key in ejbCreate()

Hello,
I'm having difficulty inserting a record into my database. The error reporting is telling me that I'm trying to insert a null value into my primary key column even though I have confirmed that the primary key column is being set in my ejbCreate() method. The method is returning the value of the primary key parameter as per an example. This value is being generated by another class in my app (i.e. it is not auto-incrementing) and passed into a create method in the servlet. If anyone can offer some guidance it would be greatly appreciated. This seems like it should be something simple but I'm having no joy.
p.s. I'm using Resin-CMP so auto-incrementing PK is not a good idea.
java.sql.SQLException: ORA-01400: cannot insert NULL into ("LEARNWARE"."SCHEDULE"."SEQUENCE_NUMBER")
Thank you.
Scott Fitzgerald

Thanks for replying. My table has six columns with one of those being the primary key (in this case sequence_number).Since the getters and setters for the field (sequenceNumber) that maps to the primary key are abstract (ala Resin-CMP), they have to be public. Changing the field definition from public to private didn't seem to do anything. I still got the same error. My deployment descriptor has the persistence type set to Container and has been all along. Any more suggestions would be greatly appreciated.
Scott Fitzgerald

Error when i set primary key to a field in table

Similar Messages

Maybe you are looking for