Sending mixed case data

Hi All,
I need to pass a field with mixed case characters ( Example : JoeSmith) .
If I dont do a TOUPPER formula for this field in Transformation at the DSO stage, the load fails with that Hex conversion message.
We don't want to convert to Uppercase for name fields.
I have set ALL_CAPITAL in RSKC ( We are on BI 7.0 SP10 Unicode system)
I tried by checking the Lower case flag for this field in the Datasource.
I am aware of Lowercase checkbox in Infoobject maintainence - and I would rather not use that.
Any ideas?
HD

I'd be looking at the input side of this. Is there a buffered stream that is not shared by the ObjectInputStream? If there is then the symptoms can be explained. A buffered stream will read in as much data as is available (up to some limit), regardless of whether that data is required. If you switch to the ObjectInputStream before the data has been consumed, then it has effectively been lost.
The 200ms delay prevents the buffered stream from consuming the extra, and makes the program work.
The solution is to ensure that the ObjectInputStream shares the buffered stream.
Sylvia.

Similar Messages

Convert data in table to mix case

Hi All,
I have a table that contains data.
This table has to columns, an id and description.
I would like to update my table to convert data to mix case.
As of now, all of my data in the table are lower case.
What I mean by mix case is first letter for each word is uppercase and the rest are lower case.
is there a function i can use ?
example:
Amended/Resentence, Type UnknownThanks

You can use the INITCAP function.
update table
set description = INITCAP(description);Example:
create table test (description varchar(50));
Table created
insert into test values ('amended/resentence, type unknown');
1 row inserted
select * from test;
DESCRIPTION
amended/resentence, type unknown
update test set description = initcap(description);
1 row updated
select * from test;
DESCRIPTION
Amended/Resentence, Type Unknown

How to preserve mixed case in Data Dictionary

Hi,
I am very new to Oracle, please excuse in advance for silly questions.
Using Oracle 9i R2, SQL Developer 1.51.5440.
I don't know if it's Oracle DB or The SQL Developer tool, but the names of the object I create are all transformed in uppercase. Table name, column names, procedure names all are displayed in uppercase. And yet I make sure when I created them to use carefully mixed case to improve readability. Example: ProductID, MyTable, etc.
I've gone over the options of SQL Developer, but I didn't see any option to turn off the automatic uppercase. Some objects still remains in mixed case, for example the content of a procedure still looks like when I typed it.
Is there a way to get the object names to be displayed exactly as I created them?
Thanks in advance.

Ok, now I see, make senses that everybody keeps using uppercase. I have tried this:
CREATE TABLE "MyTable" ("Col1" number not null, "Col2" varchar2(20) not null)
And indeed, even SELECT * FROM MyTable would not work, I have to reference the table by SELECT * FROM "MyTable"
FYI, in SQL Server, object names are case-insensitive. The name saved in the data dictionary is exactly how you type them. In the queries, constraints, indexes, etc., you can reference to the object name by any case. I find this way more convenient.
One more question, in the current schema I am working on, where all object names are uppercase. How come I can still make a query with any case?
For example if I type in SQL Developer: SELECT ProdUCTID, PrOduCTNaMe FROM T_proDuCT ;
The query executes OK although I'd expect Oracle would complain about table not found. So are the following rules correct?
1. If the object name was saved with double quote, Oracle will preserve the case and the object should always be referenced WITH double quote and the exact case.
2. If the object name was save without double quote, Oracle will uppercase the name and the object can be reference by any case.

Fetching data from database in case of mixed case in SE37

Hi,
I have created a function module(in se37) where the input is Last name(PA0002-NACHN). My requirement is i have to fetch data from PA0002 based on last name. But the problem is if i give a name in mixed case(both upper and lower) sap converts the last name into Capital letter and starts searching the database.
                  But i tried in abap editor. here SAP accept the parameter(last name) as mixed case and starts searching. Why in function module the parameters are converted into upper case. How to restrict it.
             If i will create a domain with LOWER CASE check box checked and try to call the dataelement in import part of function module then also it's converting it inot upper case. If i uncheck the lower case check box then also it's taking it as upper case.
            How to process the input parameter in function module(SE37) which should take the input as user enters,i.e if user enters small letter it should take it as small letter , if mixed letter it should take it as mixed letter and start searching.
regards
sandeep

HI sandeep,
<i>"If i will create a domain with LOWER CASE check box checked and try to call the dataelement in import part of function module then also it's converting it inot upper case. If i uncheck the lower case check box then also it's taking it as upper case."</i>
I think the data is getting converted to upper case even before it is passed to this FM.
Can yo ushow how are you testing this FM?
If you are calling this FM in a abap program using a parameter, it will convert the text to upper case as and when you enter data the name in it.
Regards,
Ravi

BUG: Export DDL and Data fails for mixed case table/column names

Hi there,
I have found a bug in SQL Developer. See details below.
Description:
When "Export DDL and Data) function is used on a table/columns not named in UPPERCASE, sql generated by SQL Developer is invalid.
Steps to reproduce:
- open SQL Developer, connect to DB
- make a table named "lowerCase" (in double quotes, so it won't be automatically changed to capital letters)
- you may also add some columns, for example "lowerCol1", "UpCol2", ALLUPCOL3
- add some data rows to the table
- choose Tools -> Export DDL and Data
- check exporting of tables and data, on "filter" tabs choose your "lowerCase" table
- press "Apply"
Error:
Generated SQL contains invalid INSERTs: mixed-case table and columns are referenced without obligatory double quotes, which yields an error when generated script is executed (see below, relevant line is underlined)
-- DDL for Table lowerCase
CREATE TABLE "DBO_HT"."lowerCase"
(     "lowerCol1" VARCHAR2(100),
     "UpCol2" VARCHAR2(100),
     "ALLUPCOL3" VARCHAR2(100)
-- DATA FOR TABLE lowerCase
-- FILTER = none used
-- INSERTING into lowerCase
Insert into lowerCase (lowerCol1,UpCol2,ALLUPCOL3) values ('lc','uc','auc');
-- END DATA FOR TABLE lowerCase
Remarks
SQL Developer: version 1.2.1, build MAIN-32.13
Oracle DBs: 9.2 & Express
OS: Windows 2000 Professional
If you need any more details/testing, let me know. I'd really appreciate a quick patch for this issue...
Alternatively, do you know of any other simple way of copying a single database (it's called a schema in Oracle, right?) from one computer to another? Possibly something so simple like detaching->copying->reattaching mdf (data) files in SQL Server... I thought that this "Export DDL&Data" function will do, but as you can see I couldn't use it.
I just need a simple solution that works - one operation on source to stuff, get the resulting files to other computer and one operation to have it running there... I think that such scenario is very basic, yet I just can't achieve it and I am simply not allowed to spend more time on it (read: our test project fails, my company rejects my "lobbying" and stays with MSSQL :/ )
Thanks a lot & bye

Thanks for your reply.
ad. 1)
You're right. I just wanted to give some very short feedback on my experiences with SQL Developer, so I didn't think starting new threads would be necessary, but as I was writing it became much bigger than I initially planned - sorry about that. I will make proper threads as soon as possible. Having "Edit post" button on this forum would also be useful.
ad. 2)
Generally, you're right - in most cases it's true that "switching DBMS is a major commitment" and "you will produce terrible code" if you don't learn the new one.
However, I think that you miss one part of market here - the market that I think Express is also targeted on. I'd call it a "fire&forget databases" market; MySQL comes to mind as possibly most common solution here. It's the rather small systems, possibly web-accessed, whose data-throughput requirements are rather modest; the point is to store data at all, and not necesarily in fastest way, because given the amount of data that is used, even on low-end hardware it will work well enough. What's important here is its general ease of use - how easy is to set up such system, connect and access data, develop a software using it, how much maintenance is needed, how easy this maintenance is, how easy are the most common development tasks as creating a DB, moving a DB from test to production server etc. There, "how easy" directly translates to "how much time we need to set it up", which translates to "how much will the development will cost".
Considering the current technology, switching the DBMS in such systems is not necesarily a major commitment and believe me that you will not produce terrible code. In many cases it's as simple as changing a switch in your ORM toolkit: hibernate.dialect = Hibernate.Dialect.OracleDialect vs MySQLDialect vs MsSql2005Dialect
Therefore, in some part of market it's easy to switch DBMS, even on project-by-project basis. The reason to switch will appear when other DBMS makes life easier => development faster. From that point of view, I can understand my colleagues giving me an embarassing look and saying "come on, I won't read all these docs just to have db copied to test server". And it doesn't mean "they are not willing to learn anything new", it's just that they feel such basic task should have self-explaining solution that doesn't require mastering any special knowledge. And if they get such simple solutions somewhere else, it costs them nothing to change the hibernate dialect.
I think Oracle did the great job with introducing the Express to this "fire&forget" market. The installation is a snap, it just works out of the box, nothing serious to configure, opposite to what I remember from installing and working on Oracle 9 a few years ago. In some places it's still "you need to start SQL*Plus and enter this script", but it's definitely less than before. I also find the SQL Developer a great tool, it can do most of what we need to do with the DB, it's also much better and pleasant to use over Oracle 9 tools. Still, a few basic things still require too much hassle, and I'd say taking your schema to another machine is one of them. So I think that, if you do it well, the "schema copy wizard" you mentioned might be very helpful. If I was to give any general advice for Express line of DB/tools, I'd say "make things simple" - make it "a DB you can't see".
That's, IMHO, the way to attract more Express users.

How to mix audio data from multiple streams without increasing in size?

For example, two clients use JMF to capture audio in linear format (content type is raw)and both send the captured data to a third client where it performs mixing to generate one data stream. Suppose each source data size is S, the mixed stream (using JMF "merge") size is S+S which is not what I want. Is there any function to generte mixed stream with size S? I don't need to the capability to reverse mixed stream back to two individual source streams.
Thanks.

S+S, ahh an academic.
This is actually a forest-trees issue here.
What your doing is appending the files, which would result in a size of 2S. What you want is somthing of size S. To do this you would need a Normilized merge. I say normalized merge because thats going to give you the best result while still avoiding out of range values.
This is easy enough to by hand if both streams S1 and S2 are of the same frequency. If they are not the same frequency, the result will be size of the larger file when convereted to whatever uniformfrequency.

Converting mixed case table name to upper case

I am migrating data from Access to Oracle and new tables and columns being created are in mixed case is there a way to convert all tablename or column name automatically.
Also does the migration workbench handle the memo fields currently defined in my oracle database.

If you want tables and columns to be created in Upper Case then make sure the Create ANSI-Compliance Names checkbox is unchecked in the options section.
1.Open Workbench.
2.Tools -> Options
Memo fields are migrated to CLOB fields in Oracle.

Issue with mix case

Hi!
Is there any way to prevent the data to be converted to upper-case without changing it's domain?
I'm trying to insert mix case in a CHAR40 domain, but the text allways returns as upper-case.
Regards,
Andre

AMadeira wrote:
> It is possible to do that using code only?
Please give more details: what you want to do programatically. ?
If you check the domain of CHAR40 thru SE11 you can find :lowercase" check box not checked. so it convert to upper case
a®

Sending IDOC creditor data to an external System

Hello,
I have a scenario where I send the creditor data from SAP to non-SAP System.
For SAP System as a target I can use the TA BD14 to do this. This is working fine. But this is not my case, I need to send on non-SAP System.
So what is the right solution for sending to an external non-SAP System? With BD14 I can only send to logical system what for me is only SAP System (right?). My workaround solution is to maintain the external non-SAP System also as logical system und choose the port as Data-Port (data will be saved on file system). Is it the best solution or there are more better known?
Where can I obtain more knowledge on intergration of external non-SAP Systems? The documentation that I have covers in 95% the issue of SAP Systems. Intergration of non-SAP Systems (or sending data to non-SAP Systems) ist more difficult as I see.
Thank you in advance. Best regards.
Michael
Edited by: Michael Swistowski on Mar 15, 2011 12:52 PM
Edited by: Michael Swistowski on Mar 15, 2011 12:53 PM
Edited by: Michael Swistowski on Mar 15, 2011 12:53 PM

Hi,
In order to send data to external system and if you have an middleware used in your landscape then
create logical system for that system and associate the port with RFC destination (based on middleware used type 3 ot type t) can be used and idoc can be sent to middleware and middleware can take care of sending the data to the external system by converting it into required format..
These are normal scenarios for which Middlewares are used for integration..
HTH
Rajesh

Create Quotation by sending different partner data to header & item table in a Report

Hello all,
   Can any one please guide me how can I send different Partner data to Header & Item by running a Z Quotation Report in SE38. Actually Now I am able to create a Quotation which takes same Partner data of Header to Item data as well but my requirement is to send different Partner data to Header & Item in a quotation.
If you have sample code for the same please do share. I will be thankful to you.
Waiting for helpful suggestions.
Regards
-Ajay

Hi Ajay,
I was referring to CRM_PARTNER_MAINTAIN_MULTI_OW and CRM_PARTNER_MAINTAIN_SINGLE_OW function modules. A sample working code (written in badi) for an order below.
l_wa_partner_com-partner_no = l_v_bp_guid.
l_wa_partner_com-partner_fct = l_c_partner_fct.
l_wa_field_names-fieldname = l_c_field_partner.
INSERT l_wa_field_names INTO TABLE l_i_input_fields.
l_wa_field_names-fieldname = l_c_field_fct.
INSERT l_wa_field_names INTO TABLE l_i_input_fields.
** Update the order with new partners
CALL FUNCTION 'CRM_PARTNER_MAINTAIN_SINGLE_OW'
EXPORTING
iv_ref_guid                    = is_orderadm_h_wrk-guid
iv_ref_kind                    = l_c_ref_kind " Pass B here in u'r case
is_partner_com            = l_wa_partner_com
CHANGING
ct_input_field_names   = l_i_input_fields
EXCEPTIONS
error_occurred             = 1
OTHERS                      = 2.
IF sy-subrc <> 0.
ENDIF.
Thanks,
Faisal

Mixed case parsing using DBMS_XMLquery

I have created a view using mixed case column names. However, when I use DBMS_XMLquery to pass the select "column_name" from table_name, it does not parse and does not work. However it works fine with passing 'select * from table_name'. Any idea how a mixed case column can be passed to dbms_xmlquery? Or any idea how a mixed case column name is passed in dynamic sql queries.

I found the problem. It was not with mixed case column names. Rather it was because of the NULL value returns from the sql query which the java procedure for transforming sql was not able to trap and throwing out exception.
However, still it is quite funny. If I use all the columns in the query or do select * , I get back the generated XML. If I just select a few columns, I get the error message
ORA-29532: Java call terminated by uncaught java exception (java.lang.NullPointerException
ORA-06512: at "SYS.DBMS_XMLQUERY" line 206
Any idea
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jinyu Wang ([email protected]):
Would you send the test case you are using for reproducing the problem?<HR></BLOCKQUOTE>
null

Mixed case table/col names and JDeveloper?

I am thinking of trying to use mixed case table/column names in my Oracle 8i database.
My hope is to achieve table/column names consistent with Java conventions (which I am happy with).
Would this work with Jdeveloper 3.1? 3.2?
Will JDeveloper/BC4J then generate mixed case names?
Will I cause my self lots of pain and suffering? (I don't consider having to enter a correct mixed case name a pain; I do consider always having to quote it and/or use TOUPPER, etc. a bit of pain)
Thanks
R.Parr
Temporal Arts
null

I do consider always having to quote it and/or use TOUPPER, etc. a bit of pain)<<<JDEV isn't as much the issue. If you have simple applications and don't intend to change things over time, or create lots of interfaces, or support multiple development tools against the same database, mixed cases seem to work fine.
To give yourself an idea of how cumbersome things will be, go in and
create "myTable" ( "myField" varchar2(20) );
now DESC ribe the table,
select myField from it.
Putting doublequotes around things all the time gets very irritating. Remember it is also for having special characters and embedded spaces... and I don't know of any PL/SQL SET ( other than the opposite: SQLCASE that forces just about everything to uppercase ).
Oh, and then you get to encounter fun things like ODBC and JDBC drivers that may or may not like it. Or if you MOVE/EXPORT the data around, your target may or may not be happy.
Working at several diversified, large organization with MANY database products/targets, I've become very disenchanted with making mixed case attributes and table names!
All tools should support mixed case correctly. Reality has returned a mixed case of results. grin or not, as the case may be.
null

Mapviewer 10.1.3.3 & 11g Database (Mixed Case Passwords)

We have an 11g Database that enforces the use of Mixed Case passwords via a Database policy applied to individual schemas. On our 10.1.3 Application server we have deployed the 10.1.3.3 Mapviewer ear and are having issue configuring the JDBC connections.
It appears that when you enter your Password in the XML config file using "!myPassword" this gets hashed but any case sensitive values are ignored meaning the connection fails when trying to establish a connection to the database i.e. the database is expecting "myPassword" and Mapviewer hands of "mypassword".
The only way around this is to use a lower case password at the database level so that Mapviewer can connect.
Is this a know issue and if so, are there any plans to use a Case Sensitive hashing algorithith in a future version of MapViewer?
Regards
Duncan

Is this the latest MapViewer kit (10.1.3.3, WebLogic certified)?
One work around is to use container data source, assuming the container (Oracle AS) can handle case sensitive database passwords.
LJ

Convert mixed case value in colum into upper case values

Hi All,
I have got a table call emp and has the following colums:
id number 10
suename_name varchar2(20)
given_name varchar2(20)
position varchar2(30)
date_hired date
Now the values in colums are mixed case and I need to change them to upper case. I think I need to use upper function to do it.
Could anyone help me by providing me sql/pl sql script to through each colum in emp table and change them to the upper case.
Many Thanks
Michael

Hi,
If you really want to try this using PL/SQL, then you'll have to use dynamic SQL, something like this untested code, since the table and column names are vaiable:
SET   SERVEROUTPUT ON SIZE 50000
DECLARE
     sql_txt     VARCHAR2 (4000);
BEGIN
     FOR r IN ( SELECT table_name
               ,       column_name
               FROM    user_tab_columns
               WHERE   data_type = 'VARCHAR2'
          --   AND     ... -- if you don't want all columns in all tables
     LOOP
          sql_txt := 'UPDATE "'
               || r.table_name
               || '" SET "'
               || r.column_name
               || '" = UPPER ("'
               || r.column_name
               || '")';
          dbms_output.put_line (sql_txt || ' = sql_txt');     -- For debugging
          -- EXECUTE IMMEDIATE sql_txt;               -- For real
     END LOOP;
END;Dynamic SQL (here) means creating a string that contains the SQL statement to be done, then using EXECUTE IMMEDIATE to run it.
Whenever you write dynamic SQL, it's a good idea to only display the SQL statement during the early stages of debugging. When it's displaying correctly, then you can try un-commenting the EXECUTE IMMEDIATE line.
Edited by: Frank Kulash on Jul 19, 2009 4:40 PM
A little more complicated, but a lot more efficient:
SET   SERVEROUTPUT ON SIZE 50000
DECLARE
     sql_txt          VARCHAR2 (4000);
BEGIN
     FOR r IN ( SELECT    table_name
               ,         column_name
               ,         ROW_NUMBER () OVER ( PARTITION BY table_name
                                  ORDER BY       column_name
                                )     AS column_num
               ,            COUNT (1)     OVER ( PARTITION BY table_name
                                )     AS total_column_cnt
               FROM      user_tab_columns
               WHERE     data_type = 'VARCHAR2'
          --   AND       ... -- if you don't want all columns in all tables
               ORDER BY table_name
               ,            column_name
     LOOP
          IF r.column_num = 1
          THEN
               sql_txt := 'UPDATE "'
               || r.table_name
               || '" SET "';
          ELSE
               sql_txt := sql_txt || ', "';
          END IF;
          sql_txt := sql_txt ||
               || r.column_name
               || '" = UPPER ("'
               || r.column_name
               || '")';
          IF r.column_num = r.total_column_cnt
          THEN     -- This is the last row for this table; run it
               dbms_output.put_line (sql_txt || ' = sql_txt');     -- For debugging
               -- EXECUTE IMMEDIATE sql_txt;               -- For real
          END IF;
     END LOOP;
END;
{code}
The difference is that the first solution produces and executes a separate UPDATE statement for each column, like this:
{code}
UPDATE "TABLE_1" SET "COLUMN_A" = UPPER ("COLUMN_A");
UPDATE "TABLE_1" SET "COLUMN_B" = UPPER ("COLUMN_B");
UPDATE "TABLE_1" SET "COLUMN_C" = UPPER ("COLUMN_C");
{code}
but it's much more efficient to do change all the columns at once, as long as you have the row in hand. So the second solution only creates one SQL statement per table, like this:
{code}
UPDATE "TABLE_1" SET "COLUMN_A" = UPPER ("COLUMN_A")
           ,   "COLUMN_B" = UPPER ("COLUMN_B")
           ,   "COLUMN_C" = UPPER ("COLUMN_C");
{code} where every line above corresponds to a row fom the query. The first line for every table will start with
{code}
UPDATE "TABLE_1" SET "but all the others will start with
{code}
and only on the last column for a given table will the statement be executed.

Mixed case queries and Lowercase and Uppercase queries

Is there any performance difference if i execute sql statements with mixed case and uppercase. what will be the fastest and why? please explain?
Please support stronlgly as one of my Coleague is arguing that there will be performance difference if you send queries either only in lowercase or only in uppercase , but not in MixEd case.
Please explain.
Thks
Raj

You Coleague seems to be a real pain in the ass.
Tell him to shut up and do something useful. Now you are being a pain by posting the same Question over and over. Multiple posts of the same Question wont solve your problem. If you are not convinced with the replies, why don't you and your colleague, both sit together and pick some big table and run sqltrace and find the result and let us know. :o)
cheers, AS

Sending mixed case data

Similar Messages

Maybe you are looking for