![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, Any idea why it is possible to work in MSAS2000 and see the data from an Oracle table but when processing with a Microsoft for Oracle / Oracle OLE DB ODBC driver then there is always an error. Regards, Marco |
#3
| |||
| |||
|
|
Hi, Any idea why it is possible to work in MSAS2000 and see the data from an Oracle table but when processing with a Microsoft for Oracle / Oracle OLE DB ODBC driver then there is always an error. Regards, Marco |
#4
| |||
| |||
|
|
Hi, Any idea why it is possible to work in MSAS2000 and see the data from an Oracle table but when processing with a Microsoft for Oracle / Oracle OLE DB ODBC driver then there is always an error. Regards, Marco |
#5
| |||
| |||
|
|
This is actually a common conceptional problem which happens even if you are using a SQL Server data source. When you are creating objects with Analysis Manager, looking at data, etc. then you are using the interactive account running under Analysis Manager as your security environment. However, when you process a dimension or partition, it isn't your process which is doing the work -- it is the MSSQLServerOLAPService service itself. This introduces several common mis-configurations. For example, if you have the service configured to be running under the Local System account, then it will be denied network access (this is a characteristic of Local System that it is unable to touch any network resources), or if you are using a domain account, it might not have access to the remote machine, or have access to Oracle, etc. The give-away is that you said this happens only when processing -- as soon as I heard that, this mis-configuration immediately came to mind. Hope that helps. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI Systems Team SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. olap (AT) gmsbv (DOT) nl> wrote in message news:1129637794.278227.71640 (AT) g47g2000cwa (DOT) googlegroups.com... Hi, Any idea why it is possible to work in MSAS2000 and see the data from an Oracle table but when processing with a Microsoft for Oracle / Oracle OLE DB ODBC driver then there is always an error. Regards, Marco |
#6
| |||
| |||
|
|
This is actually a common conceptional problem which happens even if you are using a SQL Server data source. When you are creating objects with Analysis Manager, looking at data, etc. then you are using the interactive account running under Analysis Manager as your security environment. However, when you process a dimension or partition, it isn't your process which is doing the work -- it is the MSSQLServerOLAPService service itself. This introduces several common mis-configurations. For example, if you have the service configured to be running under the Local System account, then it will be denied network access (this is a characteristic of Local System that it is unable to touch any network resources), or if you are using a domain account, it might not have access to the remote machine, or have access to Oracle, etc. The give-away is that you said this happens only when processing -- as soon as I heard that, this mis-configuration immediately came to mind. Hope that helps. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI Systems Team SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. olap (AT) gmsbv (DOT) nl> wrote in message news:1129637794.278227.71640 (AT) g47g2000cwa (DOT) googlegroups.com... Hi, Any idea why it is possible to work in MSAS2000 and see the data from an Oracle table but when processing with a Microsoft for Oracle / Oracle OLE DB ODBC driver then there is always an error. Regards, Marco |
#7
| |||
| |||
|
|
This is actually a common conceptional problem which happens even if you are using a SQL Server data source. When you are creating objects with Analysis Manager, looking at data, etc. then you are using the interactive account running under Analysis Manager as your security environment. However, when you process a dimension or partition, it isn't your process which is doing the work -- it is the MSSQLServerOLAPService service itself. This introduces several common mis-configurations. For example, if you have the service configured to be running under the Local System account, then it will be denied network access (this is a characteristic of Local System that it is unable to touch any network resources), or if you are using a domain account, it might not have access to the remote machine, or have access to Oracle, etc. The give-away is that you said this happens only when processing -- as soon as I heard that, this mis-configuration immediately came to mind. Hope that helps. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI Systems Team SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. olap (AT) gmsbv (DOT) nl> wrote in message news:1129637794.278227.71640 (AT) g47g2000cwa (DOT) googlegroups.com... Hi, Any idea why it is possible to work in MSAS2000 and see the data from an Oracle table but when processing with a Microsoft for Oracle / Oracle OLE DB ODBC driver then there is always an error. Regards, Marco |
#8
| |||
| |||
|
#9
| |||
| |||
|
|
But what is the solution to solve this. I found several issues like change the local system account of OLAP services or change the rights to the Oracle directory Home\Oracle ? Is this also a problem in MS SQL Server 2005 ? Regards, Marco Dave Wickert [MSFT] schreef: This is actually a common conceptional problem which happens even if you are using a SQL Server data source. When you are creating objects with Analysis Manager, looking at data, etc. then you are using the interactive account running under Analysis Manager as your security environment. However, when you process a dimension or partition, it isn't your process which is doing the work -- it is the MSSQLServerOLAPService service itself. This introduces several common mis-configurations. For example, if you have the service configured to be running under the Local System account, then it will be denied network access (this is a characteristic of Local System that it is unable to touch any network resources), or if you are using a domain account, it might not have access to the remote machine, or have access to Oracle, etc. The give-away is that you said this happens only when processing -- as soon as I heard that, this mis-configuration immediately came to mind. Hope that helps. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI Systems Team SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. olap (AT) gmsbv (DOT) nl> wrote in message news:1129637794.278227.71640 (AT) g47g2000cwa (DOT) googlegroups.com... Hi, Any idea why it is possible to work in MSAS2000 and see the data from an Oracle table but when processing with a Microsoft for Oracle / Oracle OLE DB ODBC driver then there is always an error. Regards, Marco |
#10
| |||
| |||
|
|
Describe the error. We use MS OLEDB fro Oracle for many years without troubles. Roman Domin Senior Consultant roman.domin (AT) adastracorp (DOT) com http://www.adastra.cz |
![]() |
| Thread Tools | |
| Display Modes | |
| |