AIR-CAP3502I-E-K9 does not join preferred controller

I have an AIR-CAP3502I-E-K9 AP that is configured for two WLAN controllers with preferred order. However the AP does not join the primary controller, but uses the secondary one instead. I have a bunch of these AIR-CAP3502I-E-K9s , majority work fine, but three of them not.
I have tried commands according to
https://supportforums.cisco.com/docs/DOC-24917
In the controller's GUI the order is properly configured. I also tried to use 'Clear All Config" option on the controller and configured the AP from the scratch, but this did not help.
Here is what I have
XXXX#sh capwap client config
configMagicMark         0xF1E2D3C4
chkSumV2                30883
chkSumV1                1073
swVer                   7.2.111.3
adminState              ADMIN_ENABLED(1)
name                    XXXX
location                YYYY
group name
mwarName                ZZZZ1
mwarIPAddress           192.168.1.1
mwarName                ZZZZ2
mwarIPAddress           192.168.1.2
mwarName
mwarIPAddress           0.0.0.0
ssh status              Enabled
Telnet status           Enabled
numOfSlots              2
spamRebootOnAssert      1
spamStatTimer           180
randSeed                0xBAC2
transport               SPAM_TRANSPORT_L3(2)
transportCfg            SPAM_TRANSPORT_DEFAULT(0)
initialisation          SPAM_PRODUCTION_DISCOVERY(1)
ApMode                  Local
ApSubMode               Not Configured
AP Rogue Detection Mode Enabled
OfficeExtend AP         [0] Disabled
OfficeExtend AP JoinMode[0] Standard
Discovery Timer         10 secs
Heart Beat Timer        30 secs
Led State Enabled       1
Primed Interval         0
AP ILP Pre-Standard Switch Support Disabled
AP Power Injector Disabled
Infrastructure MFP validation Disabled
Configured Switch 1 Addr 192.168.1.2
Configured Switch 2 Addr 192.168.1.1
non-occupancy channels:
Ethernet (Duplex/Speed) auto/auto
*Mar 1 00:14:23.001: %CAPWAP-3-ERRORLOG: Selected MWAR 'ZZZZ2'(index 1).
*Mar 1 00:14:23.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug 22 12:21:57.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246
*Aug 22 12:21:57.581: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246
*Aug 22 12:21:57.581: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
My primary one is 192.168.1.1 and secondary is 192.168.1.2, but the AP joins always the secondary one.
The lines above
Configured Switch 1 Addr 192.168.1.2
Configured Switch 2 Addr 192.168.1.1
seem to be suspicious, I would expect the reverse order, but do not know how the code did it.
The only guess is that in the very beginning the AP joined 192.168.1.2, and this was the controller I configured the AP initially from. The AP seems to maybe somehow remember this.
OS version is
swVer                   7.2.111.3
Thanks,
Vlad

Yes, this is what I am trying all the time - configure the AP to point to the WLCs I want it to join.
Firstly I did through GUI, did not work.
Secondly I used 'Clear All Config" option on the controller and configured the AP from the scratch through GUI, did not work.
Thirdly I tried through command line on the AP, did not work.
I used these commands
XXXX#capwap ap primary-base ZZZZ1 192.168.1.1
XXXX#capwap ap secondary-base ZZZZ2 192.168.1.2
XXXX#sh capwap client config
configMagicMark         0xF1E2D3C4
chkSumV2                30883
chkSumV1                1072
swVer                   7.2.111.3
adminState              ADMIN_ENABLED(1)
name                    XXXX
location                YYYY
group name
mwarName                ZZZZ1
mwarIPAddress           192.168.1.1
mwarName                ZZZZ2
mwarIPAddress           192.168.1.2
mwarName
mwarIPAddress           0.0.0.0
ssh status              Enabled
Telnet status           Enabled
numOfSlots              2
spamRebootOnAssert      1
spamStatTimer           180
randSeed                0xBAC2
transport               SPAM_TRANSPORT_L3(2)
transportCfg            SPAM_TRANSPORT_DEFAULT(0)
initialisation          SPAM_PRODUCTION_DISCOVERY(1)
ApMode                  Local
ApSubMode               Not Configured
AP Rogue Detection Mode Enabled
OfficeExtend AP         [0] Disabled
OfficeExtend AP JoinMode[0] Standard
Discovery Timer         10 secs
Heart Beat Timer        30 secs
Led State Enabled       1
Primed Interval         0
AP ILP Pre-Standard Switch Support Disabled
AP Power Injector Disabled
Infrastructure MFP validation Disabled
Configured Switch 1 Addr 192.168.1.2
Configured Switch 2 Addr 192.168.1.1
non-occupancy channels:
Ethernet (Duplex/Speed) auto/auto
XXXX#sh log
Syslog logging: enabled (1 messages dropped, 8 messages rate-limited,
                0 flushes, 0 overruns, xml disabled, filtering disabled)
    Console logging: level debugging, 61 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 67 messages logged, xml disabled,
                    filtering disabled
    Logging Exception size (4096 bytes)
    Count and timestamp logging messages: disabled
    Trap logging: level emergencies, 0 message lines logged
        Logging to 255.255.255.255(global) (udp port 514, audit disabled, link down), 0 message lines logged, xml disabled,
               filtering disabled
Log Buffer (1048576 bytes):
*Mar 1 00:00:09.424: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:09.434: *** CRASH_LOG = YES
*Mar 1 00:00:09.434: 64bit PCIE devicesSecurity Core found.
Base Ethernet MAC address: E0:5F:B9:A8:00:7F
*Mar 1 00:00:12.482: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:13.731: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:13.797: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:16.996: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:17.052: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 1024 messages)
*Mar 1 00:00:17.068: status of voice_diag_test from WLC is false
*Mar 1 00:00:19.182: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C3500 Software (AP3G1-K9W8-M), Version 12.4(25e)JA2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Fri 14-Sep-12 19:13 by prod_rel_team
*Mar 1 00:00:19.182: %SNMP-5-COLDSTART: SNMP agent on host XXXX is undergoing a cold start
*Mar 1 00:13:33.342: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:13:33.342: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:13:33.493: status of voice_diag_test from WLC is false
*Mar 1 00:13:33.632: %SSH-5-ENABLED: SSH 2.0 has been enabledlwapp_crypto_init: MIC Present and Parsed Successfully
*Mar 1 00:13:33.956: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:13:34.343: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:13:34.343: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:13:36.029: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:13:41.484: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.1.21, mask 255.255.255.0, hostname XXXX
*Mar 1 00:13:51.981: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:14:01.997: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:14:06.099: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:14:07.190: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:14:08.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:14:08.288: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:14:09.289: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:14:11.000: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 1 00:14:23.001: %CAPWAP-3-ERRORLOG: Selected MWAR 'ZZZZ2'(index 1).
*Mar 1 00:14:23.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug 23 06:07:13.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246
*Aug 23 06:07:13.578: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246
*Aug 23 06:07:13.578: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Aug 23 06:07:14.025: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug 23 06:07:14.091: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 23 06:07:14.094: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller ZZZZ2
*Aug 23 06:07:14.154: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
What I think might be the key to the problem is this
Configured Switch 1 Addr 192.168.1.2
Configured Switch 2 Addr 192.168.1.1
This is not changing no matter what I do.
Thanks,
Vlad

Similar Messages

LWAPP 1231 does not join the controller

I have LWAPP AIR-AP1231G-A-K9 that was moved from one site to the other one. It has now a different IP address taken from DHCP and its former controller does not exist any more.
I am trying to join it to the same kind of controller which is AIR-WLC4402-12-K9 with 7.0.98.0.
However the AP cannot join the controller, first I got these on the controller
0 Wed Jul 3 14:12:56 2013 AAA Authentication Failure for UserName:0014694b3ab2 User Type: WLAN USER
1 Wed Jul 3 14:12:56 2013 Failed to authorize AP with Base Radio MAC 00:14:69:4b:3a:b2. Authorization entry does not exist in Controller's AP Authorization List.
I added the MAC address of the AP into MAC filtering, and now getting these
AAA Authentication Failure for UserName:0014694b3ab2 User Type: WLAN USER
I am reading several discussions, but they seem to be related to mesh OS mismatch.
My AP is for sure not with mesh OS as it was connected to the controller before the move.
System image file is "flash:/c1200-k9w8-mx.124-23c.JA/c1200-k9w8-mx.124-23c.JA"
#sh capwap client config
swVer 7.0.98.0
Does anyone know what to do to get the AP joined to the controller ?
I had another AP where I tried to reset the LWAPP config - clear lwapp private-config, but this did not help and this AP is now constantly rebooting without allowing me to login. It looks like the only way how to wake it up would be to convert to autonomous and then back to LWAPP which is something I cannot do as I am too far from it.
Thanks,
Vlad

Hello George,
Many thanks. I have not converted the AP from autonomous to lwapp, it has been lwapp since the very beginning. We just moved this AP from one site where it was successfully joined the controller as lwapp to other site where I am trying to join the same kind of controller with the same OS, same general settings but different IPs.
I do not understand what could happen to the AP as for sure it was just shipped and not touched IT wise.
Anyway, I will try the excersise described in the link above.
Thanks,
Vlad

Does not join to any fact source issue in 10g

HI,
I am getting below issue while compiling rpd.
Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source.
Let me describe situation here.
In physical layer , i have one xx_v table . there is no join condition physical layer. But in BMM layer we have created two logical tables for single xx_v table and providing join in bmm layer. When am compiling it i'm getting an error.
The one which i have using current rpd, same rpd in production with out any warnings(Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source) and they don't have any logical level mapping in content tab. But i am using same rpd in dev instance getting warnings.
Thanks,
Mal
Edited by: user10675696 on Feb 11, 2013 3:08 AM

Hi Srini,
Please find the below warning here and we don't have an hierarchy for MTL_SYSTE_ITEMS_B
[39008] Logical dimension table Mtl System Items B has a source MTL_SYSTEM_ITEMS_B that does not join to any fact source.
I am getting this in Dev instance only but not in Production. But one rpd can be used in dev and production instances.
Thanks,
Mall

Problem with wifi roaming - printer does not join SSID

In WiFi network with 2 APs with same SSID and security setup (WPA2) working well in roaming for PCs,
samrtphone and MacBook HP printer does not join WLAN and wireless test page from the printer shows as reason that priner see more then one AccessPoint with same SSID.
Product name HP Deskjet 3070 All-in-One Printer - B611a
Model CQ191B
Serial CN192332K805MQ
Service ID 22114
Firmware version MUM1FN1117BR
Region Europe

Assuming that one of the APs runs DHCP and that the other is bridged, turn the briged AP off. Now, connect the printer to the other AP, even if you have to move the printer.
Once the printer is connected it should work fine once you turn the second AP back on.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

[39008] Logical dimension table has a source that does not join to any fact

Dear reader,
After deleting a fact table from my physical layer and deleting it from my business model I'm getting an error: [39008] Logical dimension table TABLE X has a source TABLE X that does not join to any fact source. I do have an other fact table in the same physical model and in the same business model wich is joined to TABLE X both in the physical and business model.
I cannot figure out why I'm getting this error, even after deleting all joins and rebuilding the joins I'm getting this error. When I look into the "Joins Manager" these joins both in physical as well as logical model do exist, but with consistency check it warns me about [39008] blabla. When I ignore the warning and go to answers and try to show TABLE X (not fact, but dim) it gives me the following error.
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: TABLE X.column X Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT TABLE X.column X saw_0 FROM subject area ORDER BY saw_0
There is one *"special"* thing about this join. It is a complex join in the physical layer, because I need to do a between on dates and a smaller or equal than current date like this example dim.date between fact.date_begin and fact.date_end and dim.date <= current_date. In the business model I've got another complex join
Any help is kindly appreciated!

Hi,
Have you specified the Content level of the Fact table and mapped it with the dimension in question? Ideally this should be done by default since one of the main features of the Oracle BI is its ability to determine which source to use and specifying content level is one of the main ways to achieve this.
Another quick thing that you might try is creating a dimension (hierarchy) in case it is not already present. I had a similar issue few days back and the warning was miraculously gone by doing this.
Regards

[39008] Logical dimension table ... has a source ... that does not join to

Oracle BI 11g
Hi,
I have this set of tables:
1) Table "Sales" with fields: ID, Billdate, ProductID, Amount
2) Table "Products" with fields: ID, ProductName, BrandID, TypeID
3) Table "Brands" with fields: ID, Name
4) Table "ProductTypes": ID, Name
In Physical layer I add these tables and create Physical Diagram with constraints like this:
[Brands] -------------------->[Products]
[ProductTypes] ---------->[Products]
[Products] -----------------> [Sales]
In Logical Layer I create logical table T1 Products with sources:
- LTS1 Brands,
- LTS2 ProductTypes,
- LTS3 Products
and fields:
- ProductID
- ProductName
- Brand
- ProductType
After that I create Dimention With Level-Based Hierarchy (H1 Products):
Total Products
- Brands
-- ProductTypes
--- Detail Products
When I try "Check Global Consistency" I get warning: "[39008] Logical dimension table T1 Products has a source LTS1 Brends that does not join to any fact source."
And after that when I try to make Analysis in Oracle BI, for example:
H1 Products | Amount
and then drill down item "Total Products" I receive error:
"State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail: [,Brand,,,,,,,,,]. (HY000)"
What's wrong? Where do I mistake? And why I don't get any messages about Logical Table Source LTS2 Product Type?

Hi,
you can create a single LTS for the product with the join for all 3 tables. Do you have a particular reason for the modelling that you have used?
Regards,
Gianluca

Error 39008: logical table does not join to fact source

About to lose my mind over this error!
I'm told logical table IT_WORK_ITEM_D (a dimension) does not join to any fact source, although it should show as joined to IT_WORK_ITEM_DSNPSHT_F
- I have verified the physical joins
- I have verified the business model joins
- I have created hierarchies for all logical tables joined to the fact (IT_WORK_ITEM_DSNPSHT_F)
- I have checked the Content tab for the fact table and ensured that the logical dimension is set to the lowset level.
Suggestions from here?
-John

This was helpful, although it did not solve the problem immediately.
After much consistency checking, I cleared out some of the content assignments and that seemed to work (after having not worked). I still don't feel like I identified the core problem, but it is working now.
-John

[15013] Logical table, BIDATA.W1_SYNONYM_EMPLOYEE1_D1, does not join to any

Hello all.
I have following situation.
I have a Employee table(w1_employee1_d1)
Salary table(w_salary_f) in Database.
every thing is fine when I import it in OBIEE Administration tool and use the answers.
Then I created a synonym as (w1_synonym_employee1_d1), believing that, synonyms can be used as tables/Views.
Now I imported into Physical layer and made a join in Start Schema in 'Physical Diagram'
and so far all is fine.
When I drag it in BMM layer and do a global consistency check, I get following error.
BUSINESS MODEL BIDATA:
[nQSError: 15001] Could not load navigation space for subject area BIDATA.
[15013] Logical table, BIDATA.W1_SYNONYM_EMPLOYEE1_D1, does not join to any other logical table
In BMM layer > right click the W1_SYNONYM_EMPLOYEE1_D1 > Bussiness Model Diagram > Whole Diagram
I can see the joins exists as how I made it in Physical layer.
what I am missing ? any help is appreciated.
Thanks

Ok Just for any body's information, My problem is partly resolved.
I added this in existing .RPD and it has caused the problems, which had Hirarchies and LTS and Alias tables.
However when I try a new and fresh .RPD and create a simple with synonym, that has not got this problem.
I will dig in the problems in old .RPD why there was error.
over all I must say the quest for this tests to find if I can use Synonym is been answered, using synonym in RPD is np at all.

Logical table does not join to any logical table

HI,
I want to implement Business Unit hierarchy for drill down in OBIEE so I’ve created a custom table with the hierarchy information,
I’ve imported that table in the out-of the box physical schema & defined a relationship between the W_ORG_D table & my custom INVENTRY_ORG table as INVENTRY_ORG.BU_ID = W_ORG_D. VIS_PR_BU_ID* but when I try to check in my changes I’m getting the following error.*
Logical table INVENTRY_ORG does not join to any logical table.
Kindly let me know how to resolve this error.One more doubt i have is can we import custom tables in the out of the box OBIEE mappings for SIEBEL..that is the core subject area.
Thanks,

Hi user10340125 ,
1) I think you have joined tables in physical layer, but you have not created complex join in logical layer.
Check your consistency and see what warnings you are getting.
2) Yes you can import custom tables in whatever subject area. Once you imported tables in physical layer, then they all are just objects, so you can freely play around with them. Just for best practices, make sure you follow proper naming convention for custom tables and columns..
- Vinay

[39008] Logical dimension table X has a source that does not join to any...

Hi Gurus,
I have warning:
"[39008] Logical dimension table X has a source that does not join to any fact source"
WHERE X:
PROMOTIONS,PRODUCTS, CUSTOMERS, CHANNELS
but all logical table are mapped to fact.
Eveb I can create reports for them
(The metadata was derived from OWB 11gR2, SALES_EE)
Thanks
Laszlo
Thanks for Your earlier answer as well!

Hi,
Did you create hierrarchy on that dimension.?
Add contel level in fact source to hierarrchy detail for the fact that joins the dimension.
Look at this for best practice...http://gerardnico.com/wiki/dat/obiee/hierarchy?s
Please do close your previous thread assigning points by clicking helpful or correct to the replies
Import XML file into rpd file
Thanks,
Srikanth

[39008] Logical dimension table has a source that does not join to any fac

Hi
I have a problem in BMM layer:
*[*39008] Logical dimension table X has a source Y that does not join to any fact source.*
To start with I have three tables joining to Cust (customer) table in physical layer
Cust-Seg (Segments)-------------------------------->>Cust via segment key
Cust-Geo (customer Geographics)-------------->>Cust via address key
in the BMM layer under the CUST table when I pull in Cust- seg it works fine .
But it gives an warning [39008] -if iI create a single LTS for the product with the join for all 3 tables
The Same warning appears when i import th Cust -seg table as Logical table

Have you tried this?
http://obiee11gqna.blogspot.com/2011/02/obiee-error-39008.html

Please help me out with this error:Logical dimension table D_TARGET has a source D_TARGET that does not join to any fact source.

I get the folowing error when I run the global consistency check
WARNINGS:
Business Model DAC_Measures:
[39008] Logical dimension table D_TARGET has a source D_TARGET that does not join to any fact source.
Can someone help me out please?
Thank you!

It seems your dimension is not joined to any facts. Did you check your BMM/physical joins?

Logical Dimension tabel does not join to any fact source

I want to create a new “Dimension” table. This will be an Account Geographic dimension. My Business and Physical model are setup as follows:
1.     Account Address (WC_ADDR_F) is joined to Account (W_ORG_D) which is joined to multiple Fact tables (Ex: Order Item (W_ORDERITEM_F)
2.     When I perform “Global Consistency” check it comes back with no errors or warnings.
I create the Account Geographic dimension as follows:
1.     I right click on the subject area and select New Object->Dimension and name it “Account Geographic Dimension”. I do not select or change anything else.
2.     I right click on the new dimension and select New Object->Logical Level. I name the level “All” and check the “Grand total level” check box. Nothing else is changed.
3.     I right click on the “All” level and select New Object->Child Level. I name the level “Country”, set number of elements to 200.
4.     I right click on the “Country” level and select New Object->Child Level. I name the level “State”, set number of elements to 250.
5.     I drag the “Country” element from the Logical table (Account Address) to the “Country Level” on the new Dimension (Account Geographic Dimension)
6.     I drag the “State” element from the Logical table (Account Address) to the “State Level” on the new Dimension (Account Geographic Dimension)
7.     I then select the “Country” level properties and add a new key. For the key I select the “Country” column that I just dragged up there.
8.     I then select the “State” level properties and add a new key. For the key I select the “State” column that I just dragged up there.
My goal is that when an Analyst selects the “Country” column in Answers from the “Account Address” area that the user would be able to drill down from “Country” to “State”.
When I perform “Global Consistency” I now get the following warning:
WARNINGS:
BUSINESS MODEL CCCi Analytics:
[39008] Logical dimension table Account Address has a source CCCi_Dim_WC_ADDR_F_AccountAddress that does not join to any fact source.
Why do I now get an error no the Account Address table for not connecting to a Fact table? The error message references the “Account Address” dimension table which I believe is the source to the Account Geographic Dimension. If this is the source table, why did it not get a warning message before I created the new dimension?
Thanks…

Here is the solution that I was able to get to work:
1.     I did not have to reduce the business model to a star but was able to keep it a snowflake
Final design (which was same as the original) here is the Business Model (snowflake schema)
1.     Account Hierarchy (logical) -> Account (logical) -> Order Item Fact
2.     Account Address (logical) -> Account (logical) -> Order Item Fact
In this model the logical tables Account Hierarchy and Account Address snowflake off of the Account table which joins to the Fact table. I then:
1.     Created an “Account” dimension
2.     Created a child “Account Total” level
3.     Created two (2) children off of the “Account Total” level: (1) Account Address Country and (2) Account Hierarchy Top Level
a.     Key for “Account Address Country” was the Country column from Account Address (logical)
b.     Key for “Account Hierarchy Top Level” was the Top Level Account Name from Account Hierarchy (logical)
4.     Off of “Account Address Country”:
a.     Created a (1) child off of “Account Address Country” called “Account Address State” with the State field from the Account Address (logical) as the key
b.     Created a (1) child off of “Account Address State” called “Account Address Detail” with the ROW_WID from the Account Address (logical) as the key
c.     Created a (1) child off of “Account Address Detail” with the ROW_WID from the Account (logical) as the key
5.     Off o “Account Hierarchy Top Level”:
a.     Created a (1) child off of “Account Hierarchy Top Level” called “Account Hierarchy Level 1” with the Top Account ID from Account Hierarchy (logical) as the key
b.     Created (1) child off of “Account Hierarchy Level 1” called “Account Hierarchy Detail” with the ROW_WID from “Account Hierarchy” as the key
c.     Crated a (1) child off of “Account Hierarchy Detail” with the ROW_WID from the Account (logical) as the key
The global consistency check completed with no errors or warning with this design. It appears that perhaps you need to have all of the logical table keys in the dimension path that trace to the Fact table. One other note, cannot repeat use of other columns in the dimension except for the key of the first logical table.
Please let me know if I missed something.

Logical Dim table does not join to any fact source

[39008]Logical Dimension table <table name> has a source < table name> that does not join to any fact source.
I am getting the above error when the "correct" joins have been made in both the physical and BMM diagrams. My fact tables are showing yellow as they should and my dimension tables are white like they should be. I am only getting this as a warning though when I run a request against the tables in Answers it is telling me to resolve the warnings in the admin tool.
I know this has already been posted before -- though I did not see any additional info to correct the issue. Any help is greatly appreciated.

Hi
Follow the following Step:
In BMM expend you fact table.
Expend your sources option that is present in fact table.
Now get the property of the fact table source.
In General tab Add button is present click on that
It will open new Browse window and in right bottom part it gives some table name.
select your fact table from that and click on select.
now your table will be selected nwo click on ok.
Now save this and click on Globle Chick in.
Now I think it will not give you any working msg.
If againg you have any proble then let me know.
Thanks
Siddhartha P

Source does not join to any fact source

I created a new dimension as follows:
1) Mapped Source from OLTP to Physical Layer
2) Created Alias for source
3) Create physical "Few Foreign Key" join between new source table and existing table (key to key)
4) Run consistency check with no issues.
5) Create new Logical table
6) Create new complex logical join between same two tables in Business Model
7) Join is a Right Outer Join
8) Run consistency check and receive the following warning message.
Can you please help me resolve? Thanks...
WARNINGS:
BUSINESS MODEL Marketing Contact List:
[39008] Logical dimension table OLTP Personal Communication has a source S_PER_COMM_ADDR that does not join to any fact source.

I'm still a bit confused:
Here are the steps that I understand:
1) Create Physical Alias Table (Personal Communication)
2) Create Physical Join between Personal Communication and Contact
3) Create Logical Table (Personal Communication) with physical source Personal Communication
4) Create Business Model Join between Personal Communication and Contact (right outer with Contact on right)
If i save now i get the warning message as described at the beginning.
The Business Model look like this:_
OLTP = Source of table is OLTP database
DW = Source of table is Data Warehouse
Personal Communication(OLTP Table)->Contacts(OLTP table)->Campaign Promotion(OLTP Table)->Contact Fact(DWTable)
In addition to the Contacts (OLTP) table that joins to Campaign Promotion the following other tables join to Campaign Promotion: Prospects (OLTP)
The Contact Fact table has 5 tables joined to it: Order, Service Request, Order Item Attr, Account, and Ordered Product
There are 5 Dimension Hierarchies (all created from the DW tables): Account, Contact, Order, Order Item Attr, and Ordered Product
I then try to recreate the steps indicated:
5) Right click on the new Logical Table (Personal Communication). which generates another Dimension Hierarchy: ContactDim
Since the other logical tables created from OLTP sources do not have hierarchy dimensions created I'm not sure why I'm doing this here. If someone could explain I would appreciate it?
If I select the properties for ContactDim:
a) The default root level = Contact Total
b) Tables listed are: Prospects (OLTP), Campaign Promotion (OLTP), Contact (DW), Contacts (OLTP), and Personal Communication (OLTP)
If I expand the ContactDim dimension I have a Contact Total:
Grand total level checked
Child Levels: Prospects (OLTP), Contacts (OLTP), Personal Communication (OLTP)
I then have sources for each of these below this with all fields listed and additional lists below that.
I'm stuck here and am not sure what to do. I really don't want any drill down capability but I want to elimenate the Warning message that I was getting before.
Thanks for any help that you can provide...

AIR-CAP3502I-E-K9 does not join preferred controller

Similar Messages

Maybe you are looking for