Re: RE: db file sequential read [WAS:wait event puzzler]
he is talking about altering the column in the data dictionary. Ive updated TS$ myself and its not that big of a deal. id be a bit concerned about actually altering a column. Oracle may have some underlying code that you dont know about that assumes a maximum column length = 30 or there is some modelling reason for the limit also. From: Naveen Nahata [EMAIL PROTECTED] Date: 2003/06/12 Thu AM 08:49:22 EDT To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Subject: RE: db file sequential read [WAS:wait event puzzler] What?? -Original Message- From: Senthil Kumar D [mailto:[EMAIL PROTECTED] Sent: Thursday, June 12, 2003 5:05 PM To: Multiple recipients of list ORACLE-L Subject: RE: db file sequential read [WAS:wait event puzzler] Dear Bhaskar, You can modify col$.NAME to varchar2(60) and try. If this fails, I'll give a procedure you can use that to change it to whatever size you want. Senthil Kumar Sr Oracle DBA Summitworks Technologies Pvt Ltd -Original Message- Bhaskar Viswanathan Sent: Thursday, June 12, 2003 4:00 PM To: Multiple recipients of list ORACLE-L hi, We use Oracle 8 DB. I am not a Oracle technical guy. So lemme try explaining the problem. We need to create tables with columns, whose names(column-names) are more than 30 characters long. This is being restricted because, all columns of all tables have entries in a table called 'col'. Thit table is defined as: SQL desc col Name Null?Type - TNAME NOT NULL VARCHAR2(30) COLNO NOT NULL NUMBER CNAME NOT NULL VARCHAR2(30) COLTYPEVARCHAR2(106) WIDTH NOT NULL NUMBER SCALE NUMBER PRECISION NUMBER NULLS VARCHAR2(19) DEFAULTVAL LONG CHARACTER_SET_NAME VARCHAR2(44) SQL since CNAME is defined as VARCHAR2(30), we are forced to retrict column names to a max of 30 characters long. For eg. create table T1(x31 varchar2(50)); The above statement will be rejected with the error: * ERROR at line 1: ORA-00972: identifier is too long However, the statement create table T1(30 varchar2(50)) Succeeds in creating the table; I guess this table col is created by the system itself. how can we change this size So that the 30 character restriction in column names can be avoided??? baski **Disclaimer** ** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ** * -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bhaskar Viswanathan INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Senthil Kumar D INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). DISCLAIMER: This message (including attachment if any) is confidential and may be privileged. Before opening
RE: RE: db file sequential read [WAS:wait event puzzler]
Firstly the person is new to oracle and so he should not be doing anything with the DD other than querying. Secondly I don't think changing this 30 charcter limit can be as easy as modifying col$.name. Even if it is independent of the software code and only a DD issue, and someone has tested it to be doable, the suggestion should have come with a caveat. Well I'm not a Guru so will be more than a bit concerned before doing any such thing. Regards Naveen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, June 12, 2003 7:29 PM To: Multiple recipients of list ORACLE-L Subject: Re: RE: db file sequential read [WAS:wait event puzzler] he is talking about altering the column in the data dictionary. Ive updated TS$ myself and its not that big of a deal. id be a bit concerned about actually altering a column. Oracle may have some underlying code that you dont know about that assumes a maximum column length = 30 or there is some modelling reason for the limit also. From: Naveen Nahata [EMAIL PROTECTED] Date: 2003/06/12 Thu AM 08:49:22 EDT To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Subject: RE: db file sequential read [WAS:wait event puzzler] What?? -Original Message- From: Senthil Kumar D [mailto:[EMAIL PROTECTED] Sent: Thursday, June 12, 2003 5:05 PM To: Multiple recipients of list ORACLE-L Subject: RE: db file sequential read [WAS:wait event puzzler] Dear Bhaskar, You can modify col$.NAME to varchar2(60) and try. If this fails, I'll give a procedure you can use that to change it to whatever size you want. Senthil Kumar Sr Oracle DBA Summitworks Technologies Pvt Ltd -Original Message- Bhaskar Viswanathan Sent: Thursday, June 12, 2003 4:00 PM To: Multiple recipients of list ORACLE-L hi, We use Oracle 8 DB. I am not a Oracle technical guy. So lemme try explaining the problem. We need to create tables with columns, whose names(column-names) are more than 30 characters long. This is being restricted because, all columns of all tables have entries in a table called 'col'. Thit table is defined as: SQL desc col Name Null?Type - TNAME NOT NULL VARCHAR2(30) COLNO NOT NULL NUMBER CNAME NOT NULL VARCHAR2(30) COLTYPEVARCHAR2(106) WIDTH NOT NULL NUMBER SCALE NUMBER PRECISION NUMBER NULLS VARCHAR2(19) DEFAULTVAL LONG CHARACTER_SET_NAME VARCHAR2(44) SQL since CNAME is defined as VARCHAR2(30), we are forced to retrict column names to a max of 30 characters long. For eg. create table T1(x31 varchar2(50)); The above statement will be rejected with the error: * ERROR at line 1: ORA-00972: identifier is too long However, the statement create table T1(30 varchar2(50)) Succeeds in creating the table; I guess this table col is created by the system itself. how can we change this size So that the 30 character restriction in column names can be avoided??? baski **Disclaimer** ** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ** * -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bhaskar Viswanathan INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information
RE: RE: db file sequential read [WAS:wait event puzzler]
Updating a data dictionary is simply not done. Remember, we're the DBA (you will be assimilated) and not fun loving students who can play with their alma mater's equipment. Updating the data dictionary directly would cause the database to lose support from Oracle Corp. and the perpetrator would be liable. If you want to practice turning your car around by using the emergency brake, don't do it with the company car. Other then that, updating the data dictionary directly is simply bad manners. Mladen Gogala Oracle DBA Phone:(203) 459-6855 Email:[EMAIL PROTECTED] -Original Message- Sent: Thursday, June 12, 2003 9:59 AM To: Multiple recipients of list ORACLE-L he is talking about altering the column in the data dictionary. Ive updated TS$ myself and its not that big of a deal. id be a bit concerned about actually altering a column. Oracle may have some underlying code that you dont know about that assumes a maximum column length = 30 or there is some modelling reason for the limit also. From: Naveen Nahata [EMAIL PROTECTED] Date: 2003/06/12 Thu AM 08:49:22 EDT To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Subject: RE: db file sequential read [WAS:wait event puzzler] What?? -Original Message- From: Senthil Kumar D [mailto:[EMAIL PROTECTED] Sent: Thursday, June 12, 2003 5:05 PM To: Multiple recipients of list ORACLE-L Subject: RE: db file sequential read [WAS:wait event puzzler] Dear Bhaskar, You can modify col$.NAME to varchar2(60) and try. If this fails, I'll give a procedure you can use that to change it to whatever size you want. Senthil Kumar Sr Oracle DBA Summitworks Technologies Pvt Ltd -Original Message- Bhaskar Viswanathan Sent: Thursday, June 12, 2003 4:00 PM To: Multiple recipients of list ORACLE-L hi, We use Oracle 8 DB. I am not a Oracle technical guy. So lemme try explaining the problem. We need to create tables with columns, whose names(column-names) are more than 30 characters long. This is being restricted because, all columns of all tables have entries in a table called 'col'. Thit table is defined as: SQL desc col Name Null?Type - TNAME NOT NULL VARCHAR2(30) COLNO NOT NULL NUMBER CNAME NOT NULL VARCHAR2(30) COLTYPEVARCHAR2(106) WIDTH NOT NULL NUMBER SCALE NUMBER PRECISION NUMBER NULLS VARCHAR2(19) DEFAULTVAL LONG CHARACTER_SET_NAME VARCHAR2(44) SQL since CNAME is defined as VARCHAR2(30), we are forced to retrict column names to a max of 30 characters long. For eg. create table T1(x31 varchar2(50)); The above statement will be rejected with the error: * ERROR at line 1: ORA-00972: identifier is too long However, the statement create table T1(30 varchar2(50)) Succeeds in creating the table; I guess this table col is created by the system itself. how can we change this size So that the 30 character restriction in column names can be avoided??? baski **Disclaimer** ** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ** * -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bhaskar Viswanathan INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Senthil Kumar D INET: [EMAIL PROTECTED]
