| Author | Message | ||
     Side Hero Username: Twitter Post Number: 2412 Registered: 10-2009 Posted From: 151.191.175.206 Rating: N/A |
here is the scenario: -I have a master and child tables, child has 4 columns, 1 number 2,3,4 are Varchar2(1000) . -I have a sp sitting on these tables which has a parameters for master and also for child.I have no problem in saving master caz it is always 1 record. Problem is for child the data comes as big strings and that is why parameters are of clob type. -The reason why we have clob is because Application sends us huge delimited (~) string . -In SP that huge string is split into several records and saved into the table(each time 500-1000 records). I'm fine here after split each string would not be more that 500 chars . -Problem is even though we have clob type parameter we are not able to send a string more than 16K. maa thuglak gadu ippudu 250K characters string undocchu or antha kanna peddhadhe undocchu antunnadu oka string 16k ante vatini handle cheyataniki 16 clob params kaavali (250K/16K). Oka vela ee solution kaakapothe may be file or binary data approach emanna choodali  | ||
| Maverick Hero Username: Maverick Post Number: 18321 Registered: 01-2008 Posted From: 192.146.101.71 Rating: N/A |
mama, nee scenario exact ga teliyatledu..ur target is varchar2 of how much length and what oracle error its throwing up | ||
| Side Hero Username: Twitter Post Number: 2411 Registered: 10-2009 Posted From: 151.191.175.208 Rating: N/A |
annai idhi split chesinaka sangathi , asalu problem parameters pass chesetappudu kadha ,anni parameters pettatam problem kadhu repu inka pedha string raavocchu kadha . | ||
| Maverick Hero Username: Maverick Post Number: 18320 Registered: 01-2008 Posted From: 192.146.101.71 Rating: N/A |
try varchar2(say 100 char) according to ur length currently allocated | ||
| Side Hero Username: Twitter Post Number: 2410 Registered: 10-2009 Posted From: 151.191.175.208 Rating: N/A |
yes they are allocated to bytes | ||
| Side Hero Username: Twitter Post Number: 2409 Registered: 10-2009 Posted From: 151.191.175.208 Rating: N/A |
antha peddha string lo ye character double byte choodatam kastamemo , ee post lo 1 clob parameter annanu kaani actual ga alantivi 5 vunnai . Now issue is narrowed down to 1 point that is each string could hold 16K chars, but the problem here is the application may pass more than what sp is already handling(16K*5) , one solution I can think of is increase no.of clob parameters 5 to 10 but who knows in future it could be even more. | ||
| Maverick Hero Username: Maverick Post Number: 18319 Registered: 01-2008 Posted From: 192.146.101.71 Rating: N/A |
bytes lo allocated aa? | ||
| Side Hero Username: Twitter Post Number: 2408 Registered: 10-2009 Posted From: 151.191.175.208 Rating: N/A |
Varchar2 | ||
| Maverick Hero Username: Maverick Post Number: 18318 Registered: 01-2008 Posted From: 192.146.101.71 Rating: N/A |
double byte characters unnayemo input lo choodu | ||
| Gandhiguevara Side Hero Username: Gandhiguevara Post Number: 8273 Registered: 10-2009 Posted From: 209.11.184.1 Rating: N/A |
nuvvu split chesi store chese variable datatype and length enti? | ||
| Side Hero Username: Twitter Post Number: 2407 Registered: 10-2009 Posted From: 151.191.175.208 Rating: N/A |
I have stored proc which has clob datatype parameter to handle large strings, inside sp i split tht string (string delimited with ~) and store in a table as multiple records, this is working fine until 16K length string, it is blowing up if i pass even 1 character more than that . Now situation is I don't know how big is the input string is going to be . Note:we have strict rule not to use CLOB type in the table. How to get around this situation ? oracle ki manam kotha koddhiga experts light ayyendi |
