Paramenter Value Case Sensitive Setting

Is there a setting in the pref.txt file (or any place else) to change the actions of the case sensitive setting for entering parameter values? Turning it off/on. Changing the case sensitive setting in the condition that contains the parameter does not modify the parameter value entry window functionality.
Thanks,
Jerre

Hi Jerre
I'm afraid there is no preference that can be set to control the casing of the values keyed in a parameter. You would have to do this yourself by embedding the value of the parameter into a calculation and use UPPER or LOWER accordingly.
The option you are referring to controls whether Discoverer should literally take the value keyed in the parameter as the filter for the condition or not. It does not change the casing of the parameter for other uses.
Best wishes
Michael

Similar Messages

Crystal Report - Set Parameter Value - Case sensitive

Hi, 
We are using Crystal report 2008 CR4E API to implement the crystal report in our application. When we use parameter report with different cases, the code is not setting values for all the parameter fields in the report. Kindly help us in achieving the solution.
 
In Report, SQL Command is used and a parameter is passed to the SQL. The name of the parameter is given uppercase but in the SQL Command it is given in lowercase. The report still pass the parameter to the query and it is running fine in designer.
But in our application it throws the below exception. If the parameters are defined in same case then it works fine.
 
Code: 
reportClientDocument = new ReportClientDocument(); 
reportClientDocument.setReportAppServer(ReportClientDocument.inprocConnectionString); 
reportClientDocument.open(reportName, OpenReportOptions._openAsReadOnly); 
DatabaseController dbController = reportClientDocument.getDatabaseController(); 
Tables tables = dbController.getDatabase().getTables(); 
ITable table = tables.getTable(0); 
IProcedure command = (IProcedure)table; 
ParameterFieldController paramController = reportClientDocument.getDataDefController().getParameterFieldController(); 
for (int i=0; i< command.getParameters().size(); i++) { 
 ParameterField commandParam = (ParameterField) command.getParameters().get(i); 
 String paramName = commandParam.getName(); 
 String paramValue = getParmeterValues(paramName); 
 paramController.setCurrentValue("", paramName, Integer.valueOf(paramValue)); 
} 
 
Exception: 
 Assertion Failed:
 java.lang.Throwable
 at com.crystaldecisions.reports.common.asserts.CrystalAssert.ASSERT(Unknown Source)
 at com.crystaldecisions.reports.common.asserts.CrystalAssert.ASSERT(Unknown Source)
 at com.crystaldecisions.reports.queryengine.Connection.a(SourceFile:2558)
 at com.crystaldecisions.reports.queryengine.Connection.a(SourceFile:645)
 at com.crystaldecisions.reports.queryengine.Table.a(SourceFile:2234)
 at com.crystaldecisions.reports.queryengine.Table.if(SourceFile:2161)
 at com.crystaldecisions.reports.queryengine.Table.for(SourceFile:709)
 at com.crystaldecisions.reports.queryengine.b.yk(SourceFile:512)
 at com.crystaldecisions.reports.queryengine.b.yl(SourceFile:878)
 at com.crystaldecisions.reports.queryengine.QueryInfo.vE(SourceFile:241)
 at com.crystaldecisions.reports.datafoundation.DFQuery.for(SourceFile:628)
 at com.crystaldecisions.reports.datalayer.a.do(SourceFile:1621)
 at com.crystaldecisions.reports.datalayer.a.a(SourceFile:1404)
 at com.crystaldecisions.reports.dataengine.m.b(SourceFile:334)
 at com.crystaldecisions.reports.dataengine.j.b(SourceFile:515)
 at com.crystaldecisions.reports.dataengine.m.o(SourceFile:408)
 at com.crystaldecisions.reports.dataengine.m.a(SourceFile:173)
 at com.crystaldecisions.reports.dataengine.ContextNode.a(SourceFile:114)
 at com.crystaldecisions.reports.dataengine.ContextNode.a(SourceFile:95)
 at com.crystaldecisions.reports.dataengine.j.case(SourceFile:1080)
 at com.crystaldecisions.reports.dataengine.h.<init>(SourceFile:108)
 at com.crystaldecisions.reports.dataengine.DataContext.a(SourceFile:254)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.a(SourceFile:4660)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.a(SourceFile:4574)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.new(SourceFile:2652)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.byte(SourceFile:2610)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.try(SourceFile:2282)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.int(SourceFile:2442)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.I(SourceFile:1013)
 at com.crystaldecisions.reports.formatter.formatter.objectformatter.ObjectFormatter.fo(SourceFile:526)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.if(SourceFile:613)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.a(SourceFile:578)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.X(SourceFile:387)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.moveToPageN(SourceFile:339)
 at com.crystaldecisions.reports.formatter.export2.a.a(SourceFile:78)
 at com.crystaldecisions.reports.formatter.export2.a.a(SourceFile:247)
 at com.crystaldecisions.reports.formatter.export2.ExportSupervisorEx.if(SourceFile:642)
 at com.crystaldecisions.reports.formatter.export2.ExportSupervisorEx.a(SourceFile:586)
 at com.businessobjects.reports.sdk.requesthandler.ReportViewingRequestHandler.a(SourceFile:636)
 at com.businessobjects.reports.sdk.requesthandler.ReportViewingRequestHandler.int(SourceFile:672)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1944)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:661)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:167)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:529)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:527)
 at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(SourceFile:102)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(SourceFile:525)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(SourceFile:424)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(SourceFile:352)
 at com.businessobjects.sdk.erom.jrc.a.a(SourceFile:54)
 at com.businessobjects.sdk.erom.jrc.a.execute(SourceFile:67)
 at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(SourceFile:716)
 at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(SourceFile:125)
 at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(SourceFile:537)
 at com.crystaldecisions.sdk.occa.report.application.ds.a(SourceFile:186)
 at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(SourceFile:1558)
 at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(SourceFile:337)
 at com.crystaldecisions.sdk.occa.report.application.ReportSource.export(SourceFile:286)
 at com.crystaldecisions.sdk.occa.report.application.AdvancedReportSource.export(SourceFile:209)
 at com.mysystems.myapp.common.CrystelReport.print(CrystelReport.java:387)
 at com.ibm._jsp._ShowReport._jspService(_ShowReport.java:316)
 at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:87)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
 at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1146)
 at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
 at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
 at com.mysystems.myapp.common.MyServletFilter.doFilter(MyServletFilter.java:107)
 at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
 at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
 at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
 at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:837)
 at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:680)
 at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588)
 at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
 at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
 at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:232)
 at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
 at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:748)
 at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
 at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:122)
 at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
 at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
 at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
 at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
 at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
 at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
 at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
 at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
 at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
 at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
 Rowset restart: moveToStart true
 Rowset execute
 Executing query using command text:
 Select DeptName from Dept where DeptNo = {?deptno}
 
 detected an exception: Unexpected database connector error
 ...
 Caused by: com.crystaldecisions.reports.common.QueryEngineException: Unexpected database connector error
 at com.crystaldecisions.reports.queryengine.Connection.bf(SourceFile:2958)
 at com.crystaldecisions.reports.queryengine.Rowset.z3(SourceFile:944)
 at com.crystaldecisions.reports.queryengine.Rowset.bL(SourceFile:533)
 at com.crystaldecisions.reports.queryengine.Rowset.zM(SourceFile:245)
 at com.crystaldecisions.reports.queryengine.Connection.a(SourceFile:776)
 at com.crystaldecisions.reports.queryengine.Table.a(SourceFile:2234)
 at com.crystaldecisions.reports.queryengine.Table.if(SourceFile:2161)
 at com.crystaldecisions.reports.queryengine.Table.for(SourceFile:709)
 at com.crystaldecisions.reports.queryengine.b.yk(SourceFile:512)
 at com.crystaldecisions.reports.queryengine.b.yl(SourceFile:878)
 at com.crystaldecisions.reports.queryengine.QueryInfo.vE(SourceFile:241)
 at com.crystaldecisions.reports.datafoundation.DFQuery.for(SourceFile:628)
 at com.crystaldecisions.reports.datalayer.a.do(SourceFile:1621)
 at com.crystaldecisions.reports.datalayer.a.a(SourceFile:1404)
 at com.crystaldecisions.reports.dataengine.m.b(SourceFile:334)
 at com.crystaldecisions.reports.dataengine.j.b(SourceFile:515)
 at com.crystaldecisions.reports.dataengine.m.o(SourceFile:408)
 at com.crystaldecisions.reports.dataengine.m.a(SourceFile:173)
 at com.crystaldecisions.reports.dataengine.ContextNode.a(SourceFile:114)
 at com.crystaldecisions.reports.dataengine.ContextNode.a(SourceFile:95)
 at com.crystaldecisions.reports.dataengine.j.case(SourceFile:1080)
 at com.crystaldecisions.reports.dataengine.h.<init>(SourceFile:108)
 at com.crystaldecisions.reports.dataengine.DataContext.a(SourceFile:254)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.a(SourceFile:4660)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.a(SourceFile:4574)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.new(SourceFile:2652)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.byte(SourceFile:2610)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.try(SourceFile:2282)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.int(SourceFile:2442)
 at com.crystaldecisions.reports.dataengine.DataProcessor2.I(SourceFile:1013)
 at com.crystaldecisions.reports.formatter.formatter.objectformatter.ObjectFormatter.fo(SourceFile:526)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.if(SourceFile:613)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.a(SourceFile:578)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.X(SourceFile:387)
 at com.crystaldecisions.reports.formatter.formatter.paginator.PageFormatter.moveToPageN(SourceFile:339)
 at com.crystaldecisions.reports.formatter.export2.a.a(SourceFile:78)
 at com.crystaldecisions.reports.formatter.export2.a.a(SourceFile:247)
 at com.crystaldecisions.reports.formatter.export2.ExportSupervisorEx.if(SourceFile:642)
 at com.crystaldecisions.reports.formatter.export2.ExportSupervisorEx.a(SourceFile:586)
 at com.businessobjects.reports.sdk.requesthandler.ReportViewingRequestHandler.a(SourceFile:636)
 at com.businessobjects.reports.sdk.requesthandler.ReportViewingRequestHandler.int(SourceFile:672)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1944)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:661)
 ... 49 more
 Caused by: com.businessobjects.reports.jdbinterface.common.DBException: Unexpected database connector error
 at com.crystaldecisions.reports.queryengine.driverImpl.jdbc.JDBCQueryDefinition.Execute(Unknown Source)
 at com.crystaldecisions.reports.queryengine.driverImpl.jdbc.JDBCQueryDefinition.Execute(Unknown Source)
 at com.crystaldecisions.reports.queryengine.Connection.bf(SourceFile:2953)
 ... 91 more
 Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near '?'.
 at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
 at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
 at com.mysystems.myapp.connection.StatementImplementaion.execute(StatementImplementaion.java:269)
 ... 94 more

Hi,
Can some one please help with the solution

Case Sensitive logins

Hello,
We're using Weblogic 8.1.
If I create a user, tmui. Weblogic ignores the login case when I login using
ServletAuthentication. The password is case sensitive.
How can I make the login value case sensitive as well? I should not be allowed
to login with TMUI.
thanks,
Tom

I suspect it is the authentication provider that is case-insensitive. What
authentication provider are you using? If you are using a case-insensitive
one (eg: the NT realm via the compatibility realm), then it is the realm
that is case-insensitive, not WLS.
- Neil
"Tom" <[email protected]> wrote in message
news:3ffb26eb$[email protected]..
>
Hello,
We're using Weblogic 8.1.
If I create a user, tmui. Weblogic ignores the login case when I loginusing
ServletAuthentication. The password is case sensitive.
How can I make the login value case sensitive as well? I should not beallowed
to login with TMUI.
thanks,
Tom

How to select a case sensitive value in SQL with C#

Hello,
I have an application that at the begining a user will login with a user name and password which is stored in the database. The SQL statement is as follows:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' AND passWord='" + txtPassword.Text + "'";
For testing purposes I have set the password to the word test. The problem is, if the user enters in TEST or TeSt or TESt it will grant them access. How do I set it to force the correct case?
I am using SQL 2005 for the database.
Thanks!
~zero

You can also set Collation while comparing strings:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' COLLATE Latin1_General_CS_AS AND passWord='" + txtPassword.Text + "' COLLATE Latin1_General_CS_AS";
All comments about not doing this type of quering using command string, instead of command with parameters, they are apsolutely right.
Nevertheless i will have only username as a parameter in the command and password will be return value from procedure. I will check for equality of entered password and returned one from command in C# code, and C# is case sensitive. There is a good security model implemented for password in AdventureWorks sample database for SQL Server 2005, in table Person.Contact.
That model use two fields for password, PasswordHash and PasswordSalt. PasswordSalt is randomly generated hash when password is modified and with that salt, password string is encrypted, which produce PasswordHash. So when you want to authenticate a user, execute a command that will return a row(PasswordHash and PasswordSalt) for entered username, and in application you will encrypt entered username with PasswordSalt. If generated string is equal with the one returned PasswordHash, then you have a valid login. If nothing is returned from command or they are not equal, you have invalid login.

Check Case sensitive values

A field value is coming in caps.
lf_tmp = u2018RMu2019.
I have to check this with another field lf_werks ,which always comes in small letters.
if lf_tmp   CN lf_werks .
    MESSAGE e002(zm) WITH 'The Path is wrong for the plant'
                           p_werks.
ENDIF.
This check always fails even if the values are like belowu2026
lf_tmp = u2018RMu2019.
lf_werks = u2018rmu2019.
How do I by-pass this case sensitiveness u2026.when I want to do the check.
thanks in advance

Actually, I'd do it the other way:
TRANSLATE lf_werks to UPPER CASE.
Since lf_werks can be a combination of upper and lower case, translating lf_tmp to lower case may not always work. This way you are always comparing upper case to upper case.
Rob

How to make Values in Table maintenance to be case sensitive

Table has only one field called link which is used to store the URL along mandt.
Table is maintained thru table maintenance
When I give value say http://www.abc.com/ipr/input into the table thru table maintenance, by default the contents are changed to caps
HTTP://WW.ABC.COM/IPR/INPUT like this
I pass this link to the email content and it doesnu2019t navigate thru the path mentioned.
While clicking the link in the content, it is changing to
http://www.abc.com/IPR/INPUT and asks to go to index page.
Can you help me to change all the values to be maintained as case sensitive ?
Thanks

Hai,
Use this Domain for yur URL data element TEXT150 or TEXT120 .
Yur probelm solved.
reward If usefull.
Thanks,
Durai.V

Retrieve values, irrespective of case sensitive

Hi all,
How to retrieve values, irrespective of case sensitive. For Examle,
column_value = "name" when i try to retrive by using
select * from table where column_value = 'NAME'
But when i use the following query it is working
select * from table where column_value = Lower('NAME')My request will contain upper or lower values, so irrespective of the case sensitive i need to retrieve values. How could this be possible.
Thanks

You need to apply the upper/lower function on both sides to ignore case
select * from table where lower(column_value) = Lower('NAME')
//OR
select * from table where upper(column_value) = upper('NAME')

Is there a way around Case Sensitive on Parm's? & Multiple Value Entry in Parms

Post Author: DennisC
CA Forum: General
Using Ver 10.0 with Lotus Domino -
I have a parmeter setup to pull in ALL records or by a selected value. Many of the values are in CAPS but some are not (they are mixed). From everything I have researched it appears the user must enter the value exactly like it is on the database making it Case Sensitive ---> is there a way around this. I would like to have the user just enter the value regardless of caps or no caps also
they can enter the value of "All" (pulls in all records) or "XYZ" that only pulls in records with XYZ. Is it possible (without creating an additional parm) to give the user the capability to enter "ABC" and "XYZ" and pull in all records with the value of ABC or XYZ in the data field...
thanks in advance for any help!!!!!!!!!!!!!!!!!!!

Post Author: pvierheilig
CA Forum: General
There are a couple options, along with the previous post.
First, and not sure if CR 10 has this as an option, but in XI, you can specify in the Options and Report Options to enable case-sensitivity.
Another option is to create a formula, such as UPPERCASE({table.field}) and reference the formula in the record selection. Such as ?parm = UpperCase({table.field})
I haven't had to deal with this lately, but it seems like it should work.

Setting case sensitivity for text searches

I am trying to figure out how to set case sensitivity for text searches for Oracle. I am using 8.1.7 and the documentation keeps referring me to the Basic_Lexer object. Does setting the mixed_case parameter to 'No' remove case sensitivity for the index or is there something else I need to do?

Do you recommend another field type that can be used that does not use case sensitivity?
Thank you

Case-sensitive values in an Tabular Model with a Oracle Datasource

Hi,Lets use an Oracle Database as Datasource for my Project. I use a "Select distinct ColumnA from Table" to build up a LookupTable in my Tabular Model. But it returns Dublicates!! eg:
When I fire the query from Oracle SQL Developer I got 2 Records "1N" and "1n". In the Grid View in SSDT I see 2 times "1N". ??
Collation Case Sensitive. OK, but how to solve that?
KR

Hi KR,
According to your description, you encounter the case-sensitive issue when creating SQL Server Analysis Services Tabular model project, right?
Based on my research, Tabular models have the insensitivity problem by default. The workaround for this issue is creating a empty tabular model in tabular server using the xmla below and import the tabular in SSDT.
<Create xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<ObjectDefinition>
<Database xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200" xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300">
<ID>Collation test</ID>
<Name>Collation test</Name>
<Language>1033</Language>
<Collation>Latin1_General_CS_AS</Collation>
<DataSourceImpersonationInfo>
<ImpersonationMode>Default</ImpersonationMode>
</DataSourceImpersonationInfo>
<ddl200_200:StorageEngineUsed>InMemory</ddl200_200:StorageEngineUsed>
<ddl200:CompatibilityLevel>1100</ddl200:CompatibilityLevel>
</Database>
</ObjectDefinition>
</Create>
For the detail information about it, please refer to the link below.
http://blogs.msdn.com/b/cathyk/archive/2011/10/24/making-tabular-models-more-sensitive.aspx
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

SOAPAction HTTP header case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be exactly like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

> The value of the required verb attribute indicates the HTTP verb. Common values are GET or POST, but others may be used. Note that HTTP verbs are case sensitive.
This section does not say anything about HTTP headers. GET and POST are not headers, but HTTP methods.
> Acording to my Webservice vendor, the SOAPAction are indicated into this section.
This section has nothing to do with SOAPAction
> Also, I am working with SAP Support and got this repply:
> ... Yes, the value should be SOAPAction
> instead of SOAPACTION....
I do not comment this.
You have now following possibilities:
1. Convince your vendor to accept HTTP headers according to above mentioned RFC
2. Convince SAP that to change SOAPAction
Good luck.

Case sensitive sql - table and field names

I have a weird problem.
I have a client which works with MS SQL SERVER 2000.
database collation name is: Turkish_CI_AS
at the beginning I have this sql statement:
"select value from [OWNER].setting"
but because this table exists in database as "SETTING", I get java.sql.SQLException -
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'setting'.
while I change the sql statement to:
"select VALUE from [OWNER].SETTING"
it works ok.
I uses also other databases, but it works ok with small letters.
How can avoid this problem? should I change all the sql statements to
upper case?
I will appreciate any help.
Thanks.

I am not sure about case sensitivity of tables, but as a convention, I always use table names in UpperCase separated only by _.
I don't remember this to be a problem with Oracle or Sybase.
***Annie***

Oracle 11G password case sensitive option is not working.

Hello,
I am facing problem in Oracle 11G. I installed and created a database. I disabled password case sensitive option by setting it to false (Pls see the below output). but case sensitive option is not disabled and i am not able to logon using the lower case password.
SQL> connect sys/<pwd in lower case>@<connect string> as sysdba;
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> connect sys/<pwd in uppper case>@<connect string> as sysdba;
Connected.
SQL> show parameter SEC_CASE_SENSITIVE_LOGON
NAME TYPE VALUE
sec_case_sensitive_logon boolean FALSE
Any idea.... should i open the case in the metalink ?
With Regards
Hemant Joshi.

Can you execute:
SQL> select USERNAME, PASSWORD_VERSIONS from dba_users where username = 'SYS';Have you tried reseting the sys password? When you create the password file by default the passwords stored on it are case sensitive, maybe you also need to rebuild it...
Enrique
PS. See Note:429465.1 +11g R1 New Feature : Case Sensitive Passwords and Strong User Authentication+
Edited by: Enrique Orbegozo on Oct 15, 2008 1:20 AM

Case Sensitivity Issue with Latin Characters

Hi,
The Latin Character that i am talking abt is "i",
I am trying to provide in my application the support for Azeri-Latin(Turkish family) Characters,
That is the display and the orientation of characters is perfectly fine throughout the flow of application.
But now there is a problem when selecting a data from DB using like constraint in where clause... The issue has been elaborated below...
From the set of characters there are two character in which i am facing Case Sensitivity issue...
They are as,
i ---> the capital of same is ---> İ
ı ---> the capital of same is ---> I
now in english character mapping,
for i ---> the capital is ---> I
So, this is creating an issue...
Now the test i have done is as follows,
I created a table as,
Create Table CS
CS1 VARCHAR2(20)
Following is the data that is inserted in the table,
Insert into CS values('İ');
Insert into CS values('i');
Insert into CS values('I');
Insert into CS values('ı');
now i am running the following query,
Select * from CS where lower(CS1) like lower('%&a%');
for characters "i","İ","I" it returns 3 rows, that are,
i
İ
I
and for character ı it only returns,
ı
ideally for characters "i" & "İ" should be mapped with each other and "ı" & "I" should be mapped with each other respectively.
But that is not the case.
I am using Oracle 10g
my NLS_database_parameters are as follows,
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
and at client i m using,
NLS_LANG = .AL32UTF8
any help on this issue will be appreciated,
Thanks & Regards,
Pratik

I'm not fully understand your question but I guess you may need to set up NLS_LANGUAGE, NLS_TERRITORY db parameters and client NLS_LANG.
eg client NLS_LANG=TURKISH_AZERBAIJAN.AL32UTF8 and db parameters NLS_LANGUAGE=TURKISH, NLS_TERRITORY=AZERBAIJAN
Full list of supported languages, locales see [Oracle® Database Globalization Support Guide local data subpage|http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/applocaledata.htm]
or tip2: check this: ALTER SESSION SET NLS_COMP=LINGUISTIC;
Edited by: Kecskemethy on Mar 24, 2009 3:14 AM
or you need something like this:
Example 5-16 Matching with the Base Letter Operator [==]
Expression: r[[=e=]]sum[[=e=]]
Matches:
resume<<
résumé<<
résume<<
resumé<<Oracle SQL syntax: SQL> SELECT col FROM test WHERE REGEXP_LIKE(col,'r[[=e=]]sum[[=e=]]');Edited by: Kecskemethy on Mar 24, 2009 3:20 AM

Case sensitivity in Oracle Text

I am familiar with the mixed_case parameter, and in my setup it is set to no, so all searches are case-insensitive. This is what I want 95% of the time, but is there a way to specify (at a query level) that a contains search is case sensitive?

Hi,
Would be nice, but the tokens are converted to uppercase on indexing. For example:
SQL> create table test (col1 varchar2(20));
Table created.
SQL> insert into test values ('MixEd cAsE');
1 row created.
SQL> create index test_idx on test(col1)
2 indextype is ctxsys.context;
Index created.
SQL> select token_text from dr$test_idx$i;
TOKEN_TEXT
CASE
MIXED
So, since they are actually stored/converted to uppercase there is nothing case-sensitive for your query to compare to.
On the flip side, if you index case-sensitive, the tokens are stored mixed-case.
SQL> drop index test_idx force;
Index dropped.
SQL> begin
2 ctx_ddl.create_preference('mylex', 'BASIC_LEXER');
3 ctx_ddl.set_attribute('mylex', 'mixed_case', 'yes');
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> create index test_idx on test(col1)
2 indextype is ctxsys.context
3 parameters('lexer mylex');
Index created.
SQL> select token_text from dr$test_idx$i;
TOKEN_TEXT
MixEd
cAsE
Now you can do something with your query to make it do what you want. You'd have to check performance to see if it is worth it.
Ron

Paramenter Value Case Sensitive Setting

Similar Messages

Maybe you are looking for