VLD-1005 Wrong Column Lengts - Pointless warning

If I have an attribute that's Number(4) and I want to use it as a source for a NUMBER column (no length or precision specified) then OWB gives me VLD-1005. Isn't this totally wrong? I can't think of a scenario where it would cause a problem. Can someone else come up with a good scenario?
Proposal for the developers: treat 0 length for number fields as NULL so conditions like 0<4 that would fire above will become NULL<4 and the users won't get a useless warning.

Hi
You can use the Preference to suppress such warnings, don't think it has the greatest name - some thing like 'Suppress Validation Warning VLD-1004' which is misleading but is related to VLD1004/1005/1006 all around data type checking.
You will find the option in OWB's preferences under the Generation/Validation section.
Cheers
David

Similar Messages

Delete command in SQLPLUS by use wrong column name command

Assume I have three table T1,T2 and T3 shown as follow...
sql> desc T1 ;
cusid number
name varchar2(50)
sql> select * from T1;
cusid name
1) 101 TEST1
2) 102 TEST2
3) 103 TEST3
4) 104 TEST4
sql>desc T2;
ref_cusid number
sql>select * from T2
cusid
1) 103
if I want to delete account in T1 that deleted account is in T2.
I must use query1 , it will work
query1::>
delete from T1 where cusid in (select ref_cusid from T2);
but if i type wrong by this command
query2::>
delete from T1 where cusid in (select cusid from T2);
in query 2,it should be have warning message because field cusid is not in T2.Right ? But it will delete all account in table T1.
compare query2 with query 3,
query3::>
delete from T1 where cusid in (select field_test from T2);
it will show warning message like 'ORA-00904: "FIELD_TEST": invalid identifier'
I noticed that in query2 and query3 , Different Thing is query 2 wrong column name in T2 has same name as column in T1. I wonder why it is.

I doubt very much if this is really what you did:
sql>desc T2;
ref_cusid number
sql>select * from T2
cusid
1) 103The desc command shows a column name ref_cusid. The select command shows a column title cusid, not ref_cusid.
You start by saying that you have 3 tables, without doing anything with T3. Are you sure you you haven't mixed up a copy and paste somewhere?

Managed Metadata appearing in wrong columns after Restoring a site to a new Site Collection

I've restored a site with some libraries that have Managed Metadata (MM) columns from one site collection into another site collection inside the same web app so it should all subscribe to the same Managed Metadata
Service Application.
There are two MM columns in one library, one holds a single value which is what type of document it is, the other is a general tag field that allows the user to add multiple MM values to it if they want.
What we've found is that data has randomly disappeared on some MM fields, on others it appears in the wrong column, and in other cases it appears fine.
I used native out of the box GUI backup and restored with the command line,
I've done it twice with the same result, so it’s not a one off corruption during backup. It's the same story in a different doc library based on different term sets as well.
Of all the things to not work properly, MM was probably last on my list to expect, it's knocked my confidence in it a bit, as well as worried me about future upgrades.
If anyone has any ideas over what may be the cause of this, it would be appreciated, I've read lots of blogs, but nothing quite like this has cropped up.
Thanks,
Jon

Most of the ISV offerings will allow you to 'Migrate' content from one SP location to another. I'm pretty sure AvePoint and a few others have tools specifically developed for shifting bits and pieces around SharePoint farms.
It is a limitation but the ISV tools tend to do a good job and maintain nearly full consistency.
There's scripts around that can do much/most of the migration and you could always extend them to do the same things as the ISV migration tools however the cost to do so can quickly get to the same ballpark as buying an already made tool.
Paul is also in the London office, we often work together when projects requiring his brains and my beauty crop up.

Wrong column-headline in se16n after adjustment in view (se11)

Hi together,
When I´ve just created a view in trx. se11 I made little typo when I entered the name of a view field.
Although I´ve adjusted this error, se16n still shows the wrong column headline.
I´ve already deleted the view and created it again...nothing changes. In se16 erverything is OK.
Thanks for any help

Hi,
This might be because of buffering issue. There is a standard program for deleting the ALV buffers. Don't remember the name. You can search in SCN for this.
Try to logoff and relogin. Ideally it should work.
Also you can debug SE16N and see from where the field cat is coming. I think it uses buffering parameters.
Thanks,
Vinod.

Pointless warning message

When creating a new actionscript class, you get the warning:
" The use of the default package is discouraged."
Please I beg of you, remove this. There is a terrible trend
of people misusing packages, thinking they are folders, and
generally going crazy tidying things up into hundreds of
directories. A package has motivations that concern scope and
visibility, along with organization. Please don't tempt people into
using *more* packages than necessary.
For example, to avoid the warning, you might create a package
called "classes" -- but nobody in the universe is going reuse the
"classes" package outside of that project.
It's really bad if you really consider it and understand
packages -- I hope you will remove this pointless warning.

I've got the same problem. It first showed up on Parallels 2.5. I upgraded to the Parallels 3.0, latest build and basically reinstalled everything (fresh format & install of Mac OS Leopard, then new partition / install of Win XP & Boot Camp) I installed Parallels and accepted the default configuration of my Boot Camp partition as the VM. When I launch Parallels, I get the same message that you got.
I sent this message to Parallels and they gave the the following reply today. In their mind, they've closed this issue. However, I had tried this repair with the original Parallels installation. it would work once but if I rebooted, I'd have the same problem. I have yet to troubleshoot this further. So I can't vouch if this repair will work. Here is the response from Parallels:
Hello,
If you boot from the Boot Camp Windows partition and the following
error message appears: "More than one Windows partitions are found. This
is not a standard Boot Camp configuration", please follow the steps in
the article:
http://kb.parallels.com/entry/28/472/
Thank you for contacting the Parallels Support Team. We now consider
the issue resolved but will keep this request ticket open for 5 days if
you need further assistance. If you do not feel that this issue is
closed, please contact us as soon as possible so that we can proceed
with troubleshooting.
Best regards,
Arthur
Parallels Customer Service
http://www.parallels.com
- Show quoted text -
Let me know if you get any resolution on this as I'm interested!

Wrong column entries

Hi,
I´ve a table where one column(status) includes wrong values. Stuff like this:
NC€CESSED
’@CESSED
jã€CESSED
thats all the same: PROCESSED! No other table or column is concerned.
Our driver (9.0.2.0.0) shows all data correct, if we are using the right statement, so we have no problems in production.
The right statement includes an select on all possible column values
Example:
select ... from confirmation where reserved = ... and status in('CREATED','PROCESSING FAILED','PROCESSED', 'PROCESSING')
Next one is´nt usable because cryptic data for column status would be returned:
select ... from confirmation where reserved = ...
What is the problem with this column?
THX for help. Marcus

Hi,
You can check; Number of incorrect logons for a user after which the logon procedure will terminate using this parameter.
in rz11 ,
login/fails_to_session_end
These parameters may help you.
http://help.sap.com/crmcg_en/22/41c43ac23cef2fe10000000a114084/content.htm
My question is there any way we can look the user account wrong password entries and how many times they entered the wrong password.
I don't think this is possible - to cheek , how many times the user entered the wrong password.
Even if possible , those types of messages should appear in the system log - sm21
Regards

Wrong column order.

Hi,
I am loading data from Essbase (I use report script to extract data) to flat file, and I have following issue:
My datasources, and mapping in ODi looks like that:
http://img849.imageshack.us/img849/1514/odiscreen.png
(Okresowo is data column)
I loaded data and what I found in flat file:
In column Zastaw there are data (member names) from dimension: Centrum odpowiedzialnośc (despite Pozycja is mapped here).
In column Prognoza there are data from Rok (despite Okres is mapped).
Same for all other columns.
My report script looks like this:
<SYM
{ SUPMISSINGROWS }{ SUPALL }{ TABDELIMIT }{ ROWREPEAT }{ NOINDENTGEN }{ NAMESON }
<COLUMN ("WIDOK")
"Okresowo"
<SUPSHARE
<ROW ("Pozycja", "Okres", "Rok", "Produkt", "Centrum odpowiedzialności", "Wersja", "Scenariusz","Obszar")
"Volume ex factory"
<DIMBOTTOM "Okres"
<DIMBOTTOM "Rok"
<DIMBOTTOM "Produkt"
<DIMBOTTOM "Centrum odpowiedzialności"
"Robocza"
"Prognoza"
"Brak obszaru"
Anyone faced sth similar?
Best regards,
Greg

Hi Greg,
Which technology is you staging area? And what is your IKM?
I would suggest to have a look at the insert statement generated when you execute it.
Is it normal that some columns are mapped on the source and other on the staging?
Regards,
JeromeFr

Submitted responses landing in wrong columns

Once a form is filled out and submitted the answers are coming in to the spreadsheet in random order? How do I make them in order of the actual form? For instance, form says: Name, Address, City... The answers are coming in Address, Name, City. How do I make them be submitted in order: Name, Address, City.

Hi,
You can reorder the columns in the response table by selecting them then click/drag using the gray area above the column name, as shown below.
Regards,
Brian

BUG: Wrong column name in View Object

Hello,
I've had this happen several times to me. I added an Entity Object to a View Object in the VO Wizard. I then went to the "Query" section and hit "Test" to test the SQL code generated by the VO Wizard. The test failed because the wizard had added an equality test (table1.col1 = table2.col2) to the WHERE part which used the wrong table name.
It is possible to manually fix this by putting the correct table name in the query, but you'd have to do this every time you make a change to the View Object.
What I did was to rebuild the View Object from scratch, and this time it correctly generated the SQL query. I was able to add some more Entity Objects, but then it happened again. This is really irritating because my View Object is fairly complex and it takes quite some time to remake it.
I can't give instructions on how to reproduce this because it only happens every so often. It would save a lot of frustration if someone could fix it though.
Hariolf

Hi Hariolf,
I was able to build this scenario and test the query with success. Here is the sql for the view object I created
from the following entities:
RootEO one to many association with Entity01
with Entity02
with Entity03
Entity01 one to many association with Entity04
All objects are included in the view object, here is the resulting generated sql:
SELECT RootEO.ROOTID,
RootEO.ATTR,
Entity01.EO1ID,
Entity01.ROOTID AS ROOTID1,
Entity04.EO4ID,
Entity04.ATTR AS ATTR1,
Entity02.EO2ID,
Entity02.ROOTID AS ROOTID2,
Entity03.EO3ID,
Entity03.ROOTID AS ROOTID3
FROM ROOTEO RootEO, EO1 Entity01, ENTITY04 Entity04, ENTITY02 Entity02, ENTITY03 Entity03
WHERE (((RootEO.ROOTID = Entity01.ROOTID)AND (Entity01.EO1ID = Entity04.ATTR))AND
(RootEO.ROOTID = Entity02.ROOTID))AND (RootEO.ROOTID = Entity03.ROOTID)
Let me know if I need to retest using a different scenario. Also, what version of jdeveloper are you using?
Amy

Close wrong tab with no warning

Sometimes I accidentally hit the wrong "x" on a tab and it closes it out. This is really fustrating when my mouse sticks and it closes out my college assignment I've been working on. I've checked all the setting and even went into about:config....no change. Any ideas?!

If you use "'''Ctrl+Shift+T'''" immediately you should get the tab back, and the work you had been working on in the text boxes. Even worked here.
But filling in forms is notorious across all applications for losing your work if the application goes down.
What I find frustrating in this web forum is losing my work if I accidentally open a link or bookmark in the same tab, or use Back/Forward button in the tab, and try to return with the back/forward buttons, which usually loses my data.
* Firefox and other Browser Keyboard Shortcuts (Comparison Table)<br>http://dmcritchie.mvps.org/firefox/keyboard.htm

Update Wrong Column

Receiving ORA-01407 error when attempting an update.
The ORA-01407 error is referencing the extended_cost_amt yet the SET is referring to unit_cost_amt.
Any ideas?
<pre>
UPDATE budget_detail_tbl u
SET u.unit_cost_amt =
(SELECT (ROUND ( benefit_rate_tbl.rate_amt
* s.extended_cost_amt
FROM benefit_rate_tbl,
budget_detail_tbl s,
budget_header_tbl,
(SELECT DISTINCT gl_account_tbl.gl_account_seq,
object_class_tbl.object_class_cde
FROM gl_account_tbl,
object_class_tbl,
budget_detail_tbl
WHERE budget_detail_tbl.budget_header_seq =
:p235_budget_header_seq
AND budget_detail_tbl.gl_account_seq =
gl_account_tbl.gl_account_seq
AND gl_account_tbl.object_class_seq =
object_class_tbl.object_class_seq) sub
WHERE (budget_header_tbl.budget_category_seq =
benefit_rate_tbl.budget_category_seq
AND budget_header_tbl.budget_header_seq =
:p235_budget_header_seq
AND budget_header_tbl.budget_header_seq =
s.budget_header_seq
AND benefit_rate_tbl.active_ind = 'Y'
AND budget_header_tbl.budget_category_seq =
benefit_rate_tbl.budget_category_seq
AND s.budget_yr = benefit_rate_tbl.budget_yr
AND s.gl_account_seq = sub.gl_account_seq
AND benefit_rate_tbl.target_object_class_cde =
sub.object_class_cde
AND u.budget_detail_seq = s.budget_detail_seq)
WHERE u.budget_detail_seq IN (
SELECT f.budget_detail_seq
FROM budget_detail_tbl f
WHERE f.budget_header_seq =
:p235_budget_header_seq);
</pre>
Jeff

Resolved my problem using NVL:
<pre>
UPDATE budget_detail_tbl u
SET u.unit_cost_amt =
NVL
((SELECT (ROUND ( benefit_rate_tbl.rate_amt
* s.extended_cost_amt
FROM benefit_rate_tbl,
budget_detail_tbl s,
budget_header_tbl,
(SELECT DISTINCT gl_account_tbl.gl_account_seq,
object_class_tbl.object_class_cde
FROM gl_account_tbl,
object_class_tbl,
budget_detail_tbl
WHERE budget_detail_tbl.budget_header_seq =
:p235_budget_header_seq
AND budget_detail_tbl.gl_account_seq =
gl_account_tbl.gl_account_seq
AND gl_account_tbl.object_class_seq =
object_class_tbl.object_class_seq) sub
WHERE (budget_header_tbl.budget_category_seq =
benefit_rate_tbl.budget_category_seq
AND budget_header_tbl.budget_header_seq =
:p235_budget_header_seq
AND budget_header_tbl.budget_header_seq =
s.budget_header_seq
AND benefit_rate_tbl.active_ind = 'Y'
AND budget_header_tbl.budget_category_seq =
benefit_rate_tbl.budget_category_seq
AND s.budget_yr = benefit_rate_tbl.budget_yr
AND s.gl_account_seq = sub.gl_account_seq
AND benefit_rate_tbl.target_object_class_cde =
sub.object_class_cde
AND u.budget_detail_seq = s.budget_detail_seq),
u.unit_cost_amt
WHERE u.budget_detail_seq IN (
SELECT f.budget_detail_seq
FROM budget_detail_tbl f
WHERE f.budget_header_seq =
:p235_budget_header_seq);
</pre>
Jeff

Export of subreport in wrong column

Post Author: Eany
CA Forum: Data Connectivity and SQL
I have a Crystal XI report returning 5 fields from an SP, and a 6th from a subreport.
It displays OK, but when I select File > Export > Export Report > etc etc,
I get one row with fields 1 to 5, followed by a second row, with field 6 in col A.
This is repeated throughout the export.
It is as if a CR / LF is being inserted in front of Field 6.
How can I get all 6 fields in the same row ?
Many thanks

Post Author: V361
CA Forum: Data Connectivity and SQL
Not sure if this will work.... Create a formula.
Field1 & " " & Field2 & " " & Field3 & " " & Field4 & " " & etc.....

Warning - 1241024 - Possible string truncation in column #

I am running the following command in a simple MaxL script, the output of which is sent to a text file:
display variable App.DB.SubVar;
The text file appears to have generated fine, with the substitution variable value displayed. However, the following warnings are returned each time from the stderr output. Should I be concerned? Is there any way to rectify this?
WARNING - 1241024 - Possible string truncation in column 3.
WARNING - 1241028 - Output column defined with warnings.
WARNING - 1241024 - Possible string truncation in column 4.
WARNING - 1241028 - Output column defined with warnings.

Hi John,
Many thanks for your response. The problem is a little confusing, as I cannot see how anything is being truncated here - indeed there are characters to spare! Could it be because the potential size of the substitution variable name is 320 bytes and the potential size of the substitution variable value is 256 bytes (11.1.2.1)? Could this be the cause of the warnings here?
Adding "set column_width 10;" does not appear to remove the warnings either unfortunately. Do you please have any other thoughts on how I might remove the warnings? It might allay the fears of the client later on!
James

Data Guard -- v$archive_log applied column shows wrong info

I'm playing with 10g Data Guard. Both Primary and Physical Standby are in Maximum Availability mode. When I query v$archived_log column applied for dest_id=2 (which is physical standby) for some files it shows NO value but alert log on both primary and standby shows file transferred info. Even on physical standby v$archived_log shows log is applied YES value. My question is : So why is Primary database's v$archived_log shows value NO ?
I am trying to setup crontab so that once I see value YES in primary's v$archived_log for dest_id = 2 then I can backup archived log file and delete it from primary database machine. But my perl script won't work because primary v$archived_log shows value NO for applied column for dest_id = 2.
Thanks.

Hi OrionNet,
I think I am looking at the wrong column and also on the wrong database for what I need to do. Let me explain what I am trying to achieve.
I have a shell script to check if archived logs are shipped from Primary to Standby AND if Standby successfully applied it or not. My shell script was looking at Primary databases using following query
select sequence#, archived, applied
from v$archived_log
where dest_id = 2 -- running on Primary BUT looking at standby archived log destination
order by sequence# ;
SEQUENCE# ARCHIEVED APPLIED
=====================
58 YES YES
59 YES YES
*60* YES NO
61 YES YES
After reading [v$archived_log reference entry in manual|http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_1016.htm#REFRN30011]
APPLIED Indicates whether the archivelog has been applied to its corresponding standby database (YES) or not (NO). The value is always NO for local destinations.
This column is meaningful at the physical standby site for the ARCHIVED_LOG entries with REGISTRAR='RFS' (which means this log is shipped from the primary to the standby database). If REGISTRAR='RFS' and APPLIED is NO, then the log has arrived at the standby but has not yet been applied. If REGISTRAR='RFS' and APPLIED is YES, the log has arrived and been applied at the standby database.
You can use this field to identify archivelogs that can be backed up and removed from disk.
I think I should use following query on Standby database and not on primary database
select sequence#, registrar, applied
from v$archived_log
where dest_id = 1 -- query running on standby so dest_id = 1 which is standby archive log destination
and registrar = 'RFS'
order by sequence# ;
SEQUENCE# REGISTRAR APPLIED
=====================
58 RFS YES
59 RFS YES
*60* RFS YES
61 RFS YES
So, my shell script should connect to standby database from primary database and evaluate which archive logs to delete after backup from primary machine.
Now I'll generate some gaps on Standby and check query again to make sure what I understand and expect is correct.
Hope I am clear now. Thanks for your help. My bad, I didn't read the manual correctly the first time.

Errors in the back-end database access module. OLE DB was unable to convert a value to the data type requested for column 5

Hi All,
I'm still struggling with the same cube and this is my 3rd post and once i fix some thing the other breaks. Please forgive me. When i process my cube i'm getting the error:
Errors in the back-end database access module. OLE DB was unable to convert a value to the data type requested for column 5.
My question is when the error says column 5 (is it the column 5 in the DSV?) or is it the column 5 in the DIMENSION list?
My next question is the DSV Query works perfectly fine , so why this error in cube? This is what i have in the query in DSV.
Please need help. In the below query both the column 5 (ArEASSIGNED TO VENDOR) in the CUBE and underlying table have the same data type and length VARCHAR(4000). Why is the process failing still?
SELECT [High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[compliancejoin]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_0],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[mowingsector]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_1],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[caseclosedflag]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_2],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casehasvendorinfo]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_3],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[mowingstatus]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_4],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[assignedtovendor]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_5],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[reassignedtovendor]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_6],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[currentvendor]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_7],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[invoiced]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTSInvoiced0_8],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[invoicedstatus]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_9],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casecloseddateid]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_10],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[assignedtovendordateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_11],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[reassigneddateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_12],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[currentassigneddateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_13],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[mowingduedateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_14],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[vendormoweddateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_15],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[captypename] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_16],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casetype] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTSCaseType0_17],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casenumbersubgroup] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_18],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casetownship] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_19],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casestatus] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTSCaseStatus0_20],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[caseopendateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_21],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casereferredtolegalflag]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_22],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casemacinitiatedflag] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_23],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[caseconversionstatusdesc]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_24],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[reasonforinvestigation] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_25],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[investigationopendateid]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_26],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[receiveddateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_27],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[assigned_department_staff]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_28],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[caseinitiator] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_29],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[vendorinvoiceamount] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_30],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[inspection_result] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_31],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[reason_for_complaint] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_32],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[vendor_action] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_33],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[complaint_source] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_34],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[contractcompliancevendor]
AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_35],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[invoicedstatusdateid] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_36],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[date_of_complaint_id] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_37],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[date_of_inspection_id] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_38],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[casenumber] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTSCaseNumber0_39],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[parcelnumber] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS0_40],
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[row_index] AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTSROW_INDEX0_41]
FROM (SELECT CASE Isnumeric(
accela_staging.dbo.fact_highweedsandgrassdetails.vendorinvoiceamount)
WHEN 1 THEN Cast(
fact_highweedsandgrassdetails.vendorinvoiceamount AS
VARCHAR(
10))
END AS
Total_Dollar_Amount,
fact_highweedsandgrassdetails.casenumber,
fact_highweedsandgrassdetails.row_index,
fact_highweedsandgrassdetails.mowingsector,
fact_highweedsandgrassdetails.caseclosedflag,
fact_highweedsandgrassdetails.casecloseddateid,
fact_highweedsandgrassdetails.maccomments,
fact_highweedsandgrassdetails.lastfeeinvoicedateid,
fact_highweedsandgrassdetails.casehasvendorinfo,
fact_highweedsandgrassdetails.mowingstatus,
fact_highweedsandgrassdetails.receiveddateid,
fact_highweedsandgrassdetails.assignedtovendordateid,
fact_highweedsandgrassdetails.assignedtovendor,
fact_highweedsandgrassdetails.reassigneddateid,
fact_highweedsandgrassdetails.reassignedtovendor,
fact_highweedsandgrassdetails.currentvendor,
fact_highweedsandgrassdetails.currentassigneddateid,
fact_highweedsandgrassdetails.mowingduedateid,
fact_highweedsandgrassdetails.vendormoweddateid,
fact_highweedsandgrassdetails.invoiced,
fact_highweedsandgrassdetails.invoicedstatus,
fact_highweedsandgrassdetails.invoicedstatusdateid,
fact_highweedsandgrassdetails.vendorinvoicenumber,
fact_highweedsandgrassdetails.vendorcomments,
fact_casedetails.captypename,
fact_casedetails.casenumbersubgroup,
fact_casedetails.casetype,
fact_casedetails.township AS
CaseTownship,
fact_casedetails.casestatus,
fact_casedetails.caseopendateid,
fact_casedetails.referredtolegalflag AS
CaseReferredToLegalFlag,
fact_casedetails.macinitiatedflag AS
CaseMACInitiatedFlag,
fact_casedetails.conversionstatusdesc AS
CaseConversionStatusDesc,
fact_casedetails.assignedstaff AS
CaseAssignedStaff,
fact_casedetails.completedstaff AS
CaseCompletedStaff,
fact_casedetails.closedbystaff AS
CaseClosedByStaff,
fact_casedetails.initiator AS
CaseInitiator,
fact_casedetails.reasonforinvestigation,
fact_casedetails.primaryaddress,
fact_casedetails.parcelnumber,
Cast(Datediff([day],
fact_highweedsandgrassdetails.receiveddatetime,
COALESCE (fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.recordimportdatetime)) AS
DECIMAL(6, 2))
AS
DaysOpen,
Cast(Datediff([day],
fact_highweedsandgrassdetails.receiveddatetime,
COALESCE
(fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.recordimportdatetime)) AS
NUMERIC(9, 2))
* 24 AS
HoursOpenToMow,
Cast(Datediff([day],
fact_highweedsandgrassdetails.assignedtovendordate,
COALESCE
(fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.recordimportdatetime)) AS
NUMERIC(9, 2))
* 24 AS
HoursAssignedToMow,
CASE
WHEN mowingstatus = 'Mowed'
OR mowingstatus = 'Closed' THEN 1
ELSE 0
END AS
NumberComplete,
fact_highweedsandgrassdetails.recordimportdatetime,
fact_casedetails.macsiebelnumber,
fact_highweedsandgrassdetails.mowingduedate,
fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.lastfeeinvoicedate,
fact_highweedsandgrassdetails.investigationopendatetime,
fact_highweedsandgrassdetails.investigationopendate,
fact_highweedsandgrassdetails.investigationopendateid,
Cast(Datediff([day],
fact_highweedsandgrassdetails.investigationopendatetime,
CASE
WHEN
( vendormoweddatetime IS NOT NULL
AND vendormoweddatetime <=
fact_highweedsandgrassdetails.casecloseddate ) THEN
fact_highweedsandgrassdetails.vendormoweddatetime
ELSE
CASE
WHEN (
fact_highweedsandgrassdetails.casecloseddate IS
NOT NULL
AND fact_highweedsandgrassdetails.casecloseddate
<=
fact_highweedsandgrassdetails.recordimportdatetime )
THEN
fact_highweedsandgrassdetails.casecloseddate
ELSE fact_highweedsandgrassdetails.recordimportdatetime
END
END) AS NUMERIC(9, 2)) * 24 AS
AbatementDurationHoursOLD,
Cast(Datediff([day],
fact_highweedsandgrassdetails.investigationopendatetime,
CASE
WHEN
COALESCE (vendormoweddatetime,
fact_highweedsandgrassdetails.casecloseddate) IS
NOT NULL THEN COALESCE (vendormoweddatetime,
fact_highweedsandgrassdetails.casecloseddate)
ELSE
CASE
WHEN ( fact_highweedsandgrassdetails.casecloseddate IS NOT NULL
AND fact_highweedsandgrassdetails.casecloseddate <=
fact_highweedsandgrassdetails.recordimportdatetime ) THEN
fact_highweedsandgrassdetails.casecloseddate
ELSE fact_highweedsandgrassdetails.recordimportdatetime
END
END) AS NUMERIC(9, 2)) * 24 AS
AbatementDurationHours,
fact_casedetails.assigneddepartment,
COALESCE (fact_casedetails.assignedstaff, '[null]')
+ '/'
+ COALESCE (fact_casedetails.assigneddepartment, '[null]') AS
Assigned_Department_Staff,
fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.receiveddatetime,
fact_highweedsandgrassdetails.assignedtovendordate,
fact_highweedsandgrassdetails.vendorinvoiceamount,
fact_highweedsandgrassdetails.invoicedstatusdate,
fact_highweedsandgrassdetails.complaint_source,
fact_highweedsandgrassdetails.inspection_result,
fact_highweedsandgrassdetails.reason_for_complaint,
fact_highweedsandgrassdetails.contractcompliancevendor,
fact_highweedsandgrassdetails.vendor_action,
fact_highweedsandgrassdetails.date_of_complaint_id,
fact_highweedsandgrassdetails.date_of_inspection_id,
CONVERT(INT, Replace(Replace(fact_highweedsandgrassdetails.casenumber,
'HWG', 0)
, '-', 0)) AS compliancejoin,
fact_highweedsandgrassdetails.maccomments AS Expr1,
dbo.dim_highweedscensustracts.b1_census_tract
FROM dbo.fact_highweedsandgrassdetails
INNER JOIN dbo.fact_casedetails
ON fact_highweedsandgrassdetails.casenumber =
fact_casedetails.casenumber
INNER JOIN dbo.dim_highweedscensustracts
ON fact_highweedsandgrassdetails.casenumber =
dbo.dim_highweedscensustracts.casenumber
GROUP BY fact_highweedsandgrassdetails.casenumber,
fact_highweedsandgrassdetails.row_index,
fact_highweedsandgrassdetails.mowingsector,
fact_highweedsandgrassdetails.caseclosedflag,
fact_highweedsandgrassdetails.casecloseddateid,
fact_highweedsandgrassdetails.maccomments,
fact_highweedsandgrassdetails.lastfeeinvoicedateid,
fact_highweedsandgrassdetails.casehasvendorinfo,
fact_highweedsandgrassdetails.mowingstatus,
fact_highweedsandgrassdetails.receiveddateid,
fact_highweedsandgrassdetails.assignedtovendordateid,
fact_highweedsandgrassdetails.assignedtovendor,
fact_highweedsandgrassdetails.reassigneddateid,
fact_highweedsandgrassdetails.reassignedtovendor,
fact_highweedsandgrassdetails.currentvendor,
fact_highweedsandgrassdetails.currentassigneddateid,
fact_highweedsandgrassdetails.mowingduedateid,
fact_highweedsandgrassdetails.vendormoweddateid,
fact_highweedsandgrassdetails.invoiced,
fact_highweedsandgrassdetails.invoicedstatus,
fact_highweedsandgrassdetails.invoicedstatusdateid,
fact_highweedsandgrassdetails.vendorinvoicenumber,
fact_highweedsandgrassdetails.vendorcomments,
fact_casedetails.captypename,
fact_casedetails.casenumbersubgroup,
fact_casedetails.casetype,
fact_casedetails.township,
fact_casedetails.casestatus,
fact_casedetails.caseopendateid,
fact_casedetails.referredtolegalflag,
fact_casedetails.macinitiatedflag,
fact_casedetails.conversionstatusdesc,
fact_casedetails.assignedstaff,
fact_casedetails.completedstaff,
fact_casedetails.closedbystaff,
fact_casedetails.initiator,
fact_casedetails.reasonforinvestigation,
fact_casedetails.primaryaddress,
fact_casedetails.parcelnumber,
fact_highweedsandgrassdetails.vendormoweddatetime,
Cast(Datediff([day],
fact_highweedsandgrassdetails.receiveddatetime,
COALESCE (
fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.recordimportdatetime))
AS
NUMERIC(9, 2)),
Cast(Datediff([day],
fact_highweedsandgrassdetails.receiveddatetime,
COALESCE (
fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.recordimportdatetime))
AS
NUMERIC(9, 2)),
Cast(Datediff([day],
fact_highweedsandgrassdetails.assignedtovendordate,
COALESCE (
fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.recordimportdatetime))
AS
NUMERIC(9, 2)),
CASE
WHEN mowingstatus = 'Mowed'
OR mowingstatus = 'Closed' THEN 1
ELSE 0
END,
fact_highweedsandgrassdetails.recordimportdatetime,
fact_casedetails.macsiebelnumber,
fact_highweedsandgrassdetails.mowingduedate,
fact_highweedsandgrassdetails.vendormoweddate,
fact_highweedsandgrassdetails.lastfeeinvoicedate,
fact_highweedsandgrassdetails.investigationopendatetime,
fact_highweedsandgrassdetails.investigationopendate,
fact_highweedsandgrassdetails.investigationopendateid,
Cast(Datediff([day],
fact_highweedsandgrassdetails.investigationopendatetime,
CASE
WHEN
( vendormoweddatetime IS NOT NULL
AND vendormoweddatetime <=
fact_highweedsandgrassdetails.casecloseddate ) THEN
fact_highweedsandgrassdetails.vendormoweddatetime
ELSE
CASE
WHEN (
fact_highweedsandgrassdetails.casecloseddate
IS NOT NULL
AND
fact_highweedsandgrassdetails.casecloseddate <=
fact_highweedsandgrassdetails.recordimportdatetime )
THEN
fact_highweedsandgrassdetails.casecloseddate
ELSE
fact_highweedsandgrassdetails.recordimportdatetime
END
END) AS NUMERIC(9, 2)),
Cast(Datediff(ss,
fact_highweedsandgrassdetails.investigationopendatetime,
CASE
WHEN
COALESCE (vendormoweddatetime,
fact_highweedsandgrassdetails.casecloseddate) IS
NOT NULL THEN COALESCE (vendormoweddatetime,
fact_highweedsandgrassdetails.casecloseddate)
ELSE
CASE
WHEN
( fact_highweedsandgrassdetails.casecloseddate IS NOT NULL
AND fact_highweedsandgrassdetails.casecloseddate <=
fact_highweedsandgrassdetails.recordimportdatetime ) THEN
fact_highweedsandgrassdetails.casecloseddate
ELSE fact_highweedsandgrassdetails.recordimportdatetime
END
END) AS NUMERIC(18, 2)) * 60,
fact_casedetails.assigneddepartment,
COALESCE (fact_casedetails.assignedstaff, '[null]')
+ '/'
+ COALESCE (fact_casedetails.assigneddepartment, '[null]'),
fact_highweedsandgrassdetails.casecloseddate,
fact_highweedsandgrassdetails.receiveddatetime,
fact_highweedsandgrassdetails.assignedtovendordate,
fact_highweedsandgrassdetails.vendorinvoiceamount,
fact_highweedsandgrassdetails.invoicedstatusdate,
fact_highweedsandgrassdetails.complaint_source,
fact_highweedsandgrassdetails.inspection_result,
fact_highweedsandgrassdetails.reason_for_complaint,
fact_highweedsandgrassdetails.contractcompliancevendor,
fact_highweedsandgrassdetails.vendor_action,
fact_highweedsandgrassdetails.date_of_complaint_id,
fact_highweedsandgrassdetails.date_of_inspection_id,
CONVERT(INT, Replace(
Replace(fact_highweedsandgrassdetails.casenumber, 'HWG', 0)
, '-', 0)),
fact_highweedsandgrassdetails.maccomments,
dbo.dim_highweedscensustracts.b1_census_tract) AS
[High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS]
ORDER BY [High_x0020_Weeds_x0020_and_x0020_Grass_x0020_FACTS].[compliancejoin]
ASC
SV

I just counted the columns from the top:
1) compliancejoin, 2) mowingsector, 3) caseclosedflag, 4) casehasvendorinfo, 5) mowingstatus, 6) assignedtovendor.
I see now that your subject line talks about column 6, but you say column 5 in body of your original post.
I don't know anything about cubes, but apparently there is some mapping problem when you run it from SSAS. (I assume it is SSAS, a part of the product I'm entirely ignorant of.) I figured that if you had got tripped by the zero-based numbering, you
might be staring on the wrong column.
Erland Sommarskog, SQL Server MVP, [email protected]

VLD-1005 Wrong Column Lengts - Pointless warning

Similar Messages

Maybe you are looking for