Supporting STLport in TTClasses

Hi!
How about supporting STLport in TTClasses in next version?

We had this happen when we added a new dimension to an existing application that already contained supporting detail. This supporting detail became abandoned (for lack of a better term) on the backend because it did not have a valid intersection after the new dimension was added. Yet, it still showed up in the webform. The supporting detail was red and it could not be deleted from the front-end via the webform. Being leary of writing a back-end sql update to delete this supporting detail, we handled it from the front-end using the Administration>Manage>Copy Data functionality within Planning. We simply picked a source intersection that contained no supporting detail (ie - from a future year) and copied it to the target intersection that contained the supporting detail in red. This cleared the supporting detail and we were then able to add new supporting detail without issue. We were fortunate that supporting detail was not heavily used by our end-users so it did not take too long to clear all the affected intersections.
Not sure if this will work in your case but I hope this helps.
Regards,
Craig

Similar Messages

Occi doesn't support STLPORT

When I link occi program with STLPORT, error happens:
testocci.obj : error LNK2001: unresolved external symbol "public: virtual class _STL::basic_string<char,class _STL::char_traits<char>,class _STL::allocator<char> > __thiscall oracle::occi::SQLException::getMessage(void)const " (?getMessage@SQLExcep
tion@occi@oracle@@UBE?AV?$basic_string@DV?$char_traits@D@_STL@@V?$allocator@D@2@@_STL@@XZ)
Release/testocci.exe : fatal error LNK1120: 1 unresolved externals

Hi,
i'm currently working on occi (which has such a great api than jdbc), see how i could intergate it in my db access layer in addition of the odbc one, but as we use stlport, we just can't get any success with it.
Is there any chance that Oracle will provide libraries compiled with stlport which is quite widely used today ? Maybe is there someone we could request that ?
Thank you in advance.
Adrien

Overloading ambiguity when compile with stlport

I am trying to compile code with sun compiler 5.3 with stlport 4.5.3 with sun standard iostream.
Got the following error. Is this a bug in compiler ?
"/opt/local/STLport-4.5.3/stlport/stl/_vector.c", line 76: Error: Overloading ambiguity between "_STL::uninitialized_fill_n<_STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>*, unsigned, _STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>>(_STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>*, unsigned, const _STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>&)" and "std::uninitialized_fill_n<_STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>*, unsigned, _STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>>(_STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>*, unsigned, const _STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>&)".
"/opt/local/STLport-4.5.3/stlport/stl/_vector.h", line 460: Where: While instantiating "_STL::vector<_STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>, _STL::allocator<_STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>>>::_M_fill_insert(_STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>*, unsigned, const _STL::basic_string<char, std::char_traits<char>, _STL::allocator<char>>&)".
"/opt/local/STLport-4.5.3/stlport/stl/_vector.h", line 460: Where: Instantiated from non-template code.

It's impossible to say whether the problem is in your code, the compiler, or in the STLport files without seeing the source code that you are trying to compile. Can you post a small example that illustrates the problem?
But we do not support STLport with C++ 5.3. If you have problems with that combination, you are on your own. If you can identify a compiler bug, we can try to fix it, but C++ 5.3 has been declared End Of Life, and only limited support is available.
Our recent compilers include a supported version of STLport. The current release is Sun Studio 10, but Studio 11 will be released within two weeks. Watch this space for details.
http://www.sun.com/software/products/studio/index.xml

BDB 4.5.20 build issue on Solaris 8/Forte 6.2 compiler

CC=/opt/forte-6.2/bin/CC
$../dist/configure --enable-cxx
$make
gives the following error
/usr/bin/sh ./libtool --mode=compile /opt/forte-6.2/bin/CC -c -I. -I../dist/.. -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -O ../mutex/mut_fcntl.c
mkdir .libs
/opt/forte-6.2/bin/CC -c -I. -I../dist/.. -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -O ../mutex/mut_fcntl.c -KPIC -DPIC -o .libs/mut_fcntl.o
"../mutex/mut_fcntl.c", line 21: Error: dbenv is not defined.
"../mutex/mut_fcntl.c", line 39: Error: Badly formed expression.
"../mutex/mut_fcntl.c", line 42: Error: Multiple declaration for mutex.
"../mutex/mut_fcntl.c", line 54: Error: Cannot assign void* to __db_mutexregion*.
"../mutex/mut_fcntl.c", line 133: Error: Badly formed expression.
"../mutex/mut_fcntl.c", line 136: Error: Multiple declaration for mutex.
"../mutex/mut_fcntl.c", line 146: Error: Cannot assign void* to __db_mutexregion*.
"../mutex/mut_fcntl.c", line 173: Error: Badly formed expression.
"../mutex/mut_fcntl.c", line 176: Error: Multiple declaration for mutex.
"../mutex/mut_fcntl.c", line 182: Error: "}" expected instead of EOF.
10 Error(s) detected.
*** Error code 1
make: Fatal error: Command failed for target `mut_fcntl.lo'
How can this be fixed ?

We supply STLport configured for use with our compilers with C++ 5.4 (Sun ONE Studio 7) and 5.5 (Sun ONE Studion 8 Compiler Collection). We don't support STLport for earlier compilers, and C++ 5.2 is known to have problems with STLport. I suggest upgrading to a newer compiler.

Petition to open-source OCCI

We are a large Oracle site running 10g on Solaris. We have plenty of C++ code. We are using g++ 3.4.x and we wish to use OCCI. But we can't because it's not supported with g++ on Solaris. We refuse to backport our C++ code to Sun's ancient RogueWave C++ library (non-standard) and Oracle doesn't support STLPort (also provided by Sun).
I know that there are many of you out there in a similar situation. You can't get OCCI to work with your combination of platform/compiler/std.library. For examples of exasperated users see:
Re: occi doesn't support STLPORT
Re: Lower level information
OCCI with Red Hat Enterprise Linux 3
C++ on Solaris with OCCI
I understand that it is unreasonable expect Oracle to provide binary libraries for every combination of platform/compiler/library. The solution seems clear: open-source OCCI.
The objection might be raised that this would make it hard for Oracle to provide support. In reality, most potential users of OCCI would (in my opinion) be happy to just have the opportunity of using it. The reality is that most of us that can't use it are trying to make do with (somewhat poor) open-source alternatives anyway. And Oracle can always continue to provide the "official" binaries with the current level of support.
I raised a TAR back in July '05 (4562431.993) which resulted in the creation of an Enhancement Request (4522152). This ER seems to have disappeared into a black-hole.
If you want Oracle to be more responsive to your needs with respect to OCCI, then please reply to this message. Hopefully, someone at Oracle will realise that their customers have an unfulfilled need here and act upon it.
Cheers,
Mike.
mlambrellis(AT)powercor.com.au

Please add my name to the petition.
I also tried a tar.
The Oracle person added all my comments to the ER, but the occi people basically said
"libocci is not supported in SuSE 10.1"
Here is some of what I sent originally for everyone's edification:
We are trying to build a large 64 bit C++/Qt/OCCI application on
SuSE 10.1 Linux. Here's a 'uname -a':
Linux grima 2.6.16.21-0.13-smp #1 SMP Mon Jul 17 17:22:44 UTC 2006 x86_64 x86_64 x86_64
SuSE 10.1 comes with gcc 4.1 and uses libstdc++.so.6.x.x. All
the kde/qt libs have been compiled against libstdc++.so.6.x.x.
libstdc++.so.6.x.x is not compile-time compatible with
libstdc++.so.5.x.x. As far as we know, there is NO 64-bit
libocci library available that links against libstdc++.so.6.x.x
from any of oracle's public downloads. Thus, our application
will not link. This is unacceptable.
SuSE provides a libstdc++.so.5.x.x for backwards compatibility.
If we link our app explicitly to the older libocci, we get a
compile-time warning and a run time crash.
We need Oracle to
1) Release the source code for OCCI under an LGPL license or
similar so that we and others can compile libocci ourselves
for whatever version of compiler/libstc++/platform.
or, minimally.
2) make sure all major distros' versions of
gcc/libstdc++/platform are tracked and a version of libocci
exists for public download for each.
This is a repeat of the gcc 2.96 fiasco that existed several
years ago when one could not compile an occi program against gcc
3.x because there the only libocci versions available had been
linked against the incompatible 2.96 version.
Please release source code!

TTClasses interface for PL/SQL procedure and fetching its results

Hi experts,
I am using TimesTen Release 11.2.1.3.0;
I created a simple PL/SQL procedure as follows in timesten-
Command> create or replace procedure employee(eno in emp.empno%type) is
> e_name emp.ename%type;
> begin
> select ename into e_name from emp where emp.empno = eno;
> dbms_output.put_line(e_name);
> end;
> /
And then I call it through TTClasses as
TTCmd cmd, compilecmd;
compilecmd.Prepare(conn,"alter procedure employee compile;",status);
cmd.Prepare(conn,"begin employee(1020); end;",status);
cmd.Execute(..);
cmd.FetchNext(..);
Here fetchNext is returning an error -
[TimesTen][TimesTen 11.2.1.3.0 ODBC Driver]Invalid cursor state
*** ODBC Error/Warning = 24000, TimesTen Error/Warning = 0
*** Unable to fetch row for statement: <begin employee(1020); end;>.terminate called after throwing an instance of 'TTError'
Aborted
How can I run PL/SQL procedures/functions on TimesTen through TTClasses interface?
Any help or input would be of great value.
Thanks

The issue here is nothing to do with TTClasses. Your PL/SQL procedure executes a SELECT statement (that returns just one row) using an implicit cursor within the PL/SQL procedure and retrieves the value of the ename column into the PL/SQL variable. However it does not them do anything with that value such as pass it back to the caller...
Similarly, the TTClasses code executes a statement that it is expecting to create an ODBC level cursor 9which thsi PL/SQL invocation will not of course) and it is then trying to fetch from a cursor that does not exist.
I would recommend that you take a look at the TimesTen PL/SQL documentation (Oracle® TimesTen In-Memory Database PL/SQL Developer's Guide Release 11.2.1) and refer to the section on IN, OUT and IN/OUT parameters. This will show you how you can use OUT parameters to return values to the caller. This technique works fine for ODBC, JDBC and OCi programs but does not sadly currently work with TTClasses. TTClasses has not yet been enhanced to support OUT and INOUT parameters. Of course as you have the source code for TTClasses you could make the necessary modifications yourself.
I will open a bug requesting that TTClasses support OUT and INOUT parameters but in the meantime if you need this kind of capability you will need to either modify TTClasses yourself or switch to using a different API.
Chris

Future support for C++0x in Sun Studio

I've recently been having to defend my choice of using the sun studio compiler against several gcc advocates here in the office. The one reasonable issue they keep bringing up is when the upcoming C++0x (more like C++1x or even C++2x at the pace the standards committee is operating at) features will be available in complete fashion in sun studio. They say, and I have to begrudgingly agree, that judging by the amount of time it took studio to support boost (template templates, certain partial template specializations, etc), there could be a long delay between the release of gcc's C++0x support and that of studio's.
I understand that many of the new features of C++0x, even from initial glance, appear to be quite complicated, especially lambda functors and their associated []/auto return types, variadac template parameters and class concept checking. In addition, I understand gcc has an unfair advantage so to speak since it is being used as the test bed for many of the committee proposal submitter's proof-of-concept implementations (the variadic template parameter feasibility implementation written for gcc comes to mind).
Could a developer please assuage my fears and inform me that the studio team has a roadmap/timeframe in place to release a studio that fully supports the new language-level features in a reasonably competitive time frame? It apparently will be the responsibility of the STLPort team to essentially copy many of boost's libraries (shared_ptrs, random numbers, type_traits) and rename them and move them to the std namespace and also supply the new unordered<> containers, to name a few.
I for one can't wait until boost::mpl, boost::fusion, boost::format and others are all reduced from 10's of 1000's of lines of pre-processor generated crufty template definitions to a single variadic template declaration. Also, I won't feel quite so willfully derelict to efficient code every time i bust out an std::for_each and drop in a boost::bind generated functor and instead can use a lambda function with the various efficiency gains ranging from direct referencing to the stack variables passed in as the closure arguments to the ability for the compiler to actually inline the body of the lambda function where appropriate.
I'm in no way trying to accuse you compiler developers of being slow to implement features, but just would like to be assured that there is nothing to worry about and there is a plan and current work being done on the required features. I know it's still a couple of years off, but I personally can't wait to replace hundreds of lines of boost::bind() calls with their more efficent lambda equivalent, and in addition clean up interfaces that could have used boost::bind if it weren't for the unacceptable overhead introduced often executed blocks of code.
Thanks,
Chris Knight - Faithful sun studio user through at least 2 major name changes and since at lest when it was called Forte 4.2 and RougeWave and classicIO libraries roamed the earth in vast quantities.
P.S. I truly fear that the other 3 major compilers (gnu, intel, ms) will be out the door with C++0x in around the same time and boost will then willingly drop support for the sun compiler if it doesn't support the required language features at that time as they had no problem not supporting studio at all until Studio 12 so I'm sure as soon as the 3 compilers they run nightly tests with support it, they'll be just as eager to
make use of the new features as I am.
This leaves someone who has based their entire system on Solaris + SunStudio + Boost in a potentially undesirable situation. Solaris is far too stable and Linux to ever-changing to ever consider Linux as a platform for critical systems yet the idea of running g++ on Solaris w/ gcc's propensity to change their ABI on a weekly basis gives me immediate heartburn.
Thanks again.

You raise some very good points, and believe me, we are even more aware of them than you are!
Short answer: We are planning to bring out a compiler conforming to C++0X in a timely fashion.
Longer answer:
Right now, we are working on providing binary compatibility with g++ as an option in the next compiler release. When we are done, you will be able to use g++ headers with Sun C++, and link the code with binaries created by g++. The first implementation will be on Linux. (Which versions of g++ and which versions of Linux? Stay tuned.)
Implementing all the new features of C++0X will require a re-design of parts of the compiler front end. The current compiler organization does not support "concepts", for example. (We've been looking for an excuse to re-design the front end for a while, and C++0x is not just an excuse -- it's a requirement.) With the g++ ABI work done, we'll ready to start the re-design, and begin to implement C++0x features.
We won't release an official (stable, fully-supported) product with C++0X features until the standard is final. Until then, any feature could change in unpredictable ways. We got caught by that problem with C++ 4.2 and C++98 -- we implemented what we thought were final features that changed dramatically after we released the compiler. We won't do that again. Compiler stability is one of our most important considerations.
Beginning some time next year, we expect to have Express releases with some C++0X features. Express releases are our way of providing compilers with experimental features that might not be stable yet. It gives our customers a chance to try them out and provide feedback before they become part of a stable release. That is to say, a feature flagged as experimental is subject to change, and compatibility with other Express or official releases is not guaranteed. We can therefore fix bugs and catch up with late changes in the Standard as necessary.
We have not yet done all the planning for our C++0X compiler, so I can't give you any estimates about specific feature availability and time frames. When we are farther along, we'll post the road map on a public site, and I'll announce it here.
Steve Clamage
Sun C++ Team

SunStudio 9 and modified STLport 4.5

ok folks,
my development team uses a modified version of STLport ( we have made some usability enhancements to <rope> and pthread.h and pthread.c) but we are having a really tough time compiling it using the SunStudio 9 compiler. When we contacted the sun support people they said we would have to "rename" the standard headers that STLport provides to have a weird extension (e.g. iostream.SUNWcch?). However, even when we tried the workaround, we still ended up with weird compiler errors. NB: I am also compiling this same code on HPUX (using aCC), IBM (using VA7), linux(g++), and win32 (vc6sp6) .... I have no idea why SS9 will not allow you to override the compiler provided c++ standard headers. In the end, STLport (again, not the one bundled with SS9) includes the compiler c++ headers, so why all this fuss about renaming headers?
It would help if I could here other people's opinions on how they solved this problem (ie if they have modified STLport directly and are trying to compile it into a library)

We support the version of STLport that we ship with the compiler. We also allow complete replacement of the C++ standard library. Be we do not support modification of what we ship with the compiler.
If you modify or attempt to override the headers in the supplied STLport, the headers will no longer match the libstlport supplied with the compiler, which is linked automatically when you use the -library=stlport4 option. If you don't get link-time failures, you may get run-time failures.
Instructions for replacing the C++ standard library are in the C++ User's Guide, section 12.7 "Replacing the C++ Standard Library". To find the User's Guide, point your browser to <install-dir>/SUNWspro/docs/index.html and follow the link. By default, <install-dir> is /opt. Or you can find the manual at docs.sun.com.

Multithreading and ttclasses

Being a newcomer to TT, I would like to know if:
Do the client libraries (such as ttclasses) support multithreaded clients (pthreads)? I did not see anything in the docs.
If it is supported, is there anything at all special that has to be followed and are there any restrictions?

Yes, all TimesTen APIs are thread safe. In general you will need to link your application with the relevant platform threading library (e.g, libpthread.so). For best results you should code your application to avoid sharing database connections between different threads in an arbitrary fashion. Either use one connection per thread or use a propoerly implemented connection pool. Sharing connections between threads in any other way can make code hard to underdstand and debug and can give rise to unexpected (though not incorrect) behaviours.
Chris

Platform support

I am unable to find any documentation on what platforms OCCI is supported on and what the platform-specific requirements are.
Specifically, I'd like to know which flavors of Linux and Solaris are supported, compilers/glibc requirements etc.
In addition, I see references in the OCCI documentation to STL - e.g. OCCI uses STL exceptions. Is there a particular version/vendor of STL that OCCI requires? Can I use it with STLport?

Goto www.metalink.oracle.com
Top TechDocs -> Oracle Call Interface -> certified compilers(Note:43208.1)

TTClasses C++ Shared Objs Names And gcc Compiler Versions

3 versions of the TTClasses libraries are shipped with TimesTen due to the fact that gcc 3.2, 3.4. and 4.1 produce binaries that are not compatible with each other. For instance with 7.0.2 has the following libraries:
libttclasses.so.gcc323
libttclasses.so.gcc346
libttclasses.so.gcc410
It appears the naming convention of these libraries indicates the gcc compiler version out to 3 digits that TimesTen used to create the libraries.
As new releases of TimesTen occur, when will the names of these 3 libraries change, i.e. when will TimesTen use a different version of the gcc compiler?
It appears that in 7.0.2, 7.0.2.2, and 7.0.3, the names of libraries don't change. Would it only be possible for them to change for a major release, i.e. 7.X. Could it change for a minor release like 7.0.3.X or 7.0.X?
The reason that I'm asking this is as follows:
- When the TimesTen installer is run, it checks version of the gcc compiler, then it creates a symbolic link to the appropriate lib for that version of the compiler. It names this link libttclasses.so.
- Up to now we have been linking our programs with libttclasses.so.
- However when TimesTen is run on a machine without a compiler (which is the situation in our QA and prod environment), it appears to create a link to the gcc 3.2 lib.
- This is a problem for us on Red Hat 4.0 because the default compiler is 3.4 which is what we are using, but the installer is creating a link to libttclasses.gcc323 when there is no compiler on Red Hat 4.0.
- This causes our programs to crash.
- To eliminate this we are considering linking directly with the appropriate library, i.e. libttclasses.gcc346 in our case.
- However, we dont want to have to recompile or relink or application for future minor releases of TimesTen, i.e. 7.0.3.X or 7.0.X.
- If the names of these files could change in minor releases, then we'd need to relink.
Does anyone know the answer to this?
Thanks.

As you say, the names of the libraries comes directly from the GCC version used to build them. These names (i.e. GCC vesions) will not change between minor releases. Over time and major releases will tend to drop support for older GCC versions and add support for newer versions.
Our strong recommendation is that you change the symbolic link to make libttclasses.sp point to the correct library and then link with libttclasses.so. This is the simplest and most 'future proof' method.
Chris

Error while creating a support message in satellite system

Hi,
I am facing an error while sending a support message to solman form the satellite system
(( Error Description : Error in Local Message System: Error when opening
an RFC connection Message was Not Created ))
1) I gone through various threads and set the required authorizations like
SAP_SUPPDESK_CREATE and
SAP_SV_FDB_NOTIF_BC_ADMIN ,
SAP_SUPPDESK_ADMIN
for the user in the solman .
2) I checked the RFC connection and it is working fine.
Anyone pls help me to resolve this issue

hi rohit,
thanks for u r immmediate response
do i have to assign the roles to the user in the satellite system or the solman.
some roles in those 4 roles are not in the satellite system.
thanks
Rahul

Cannot install windows 8.1 on imac 5k - apple support says "Correct, that machine can't install windows" Boot camp fail

I have a brand new imac 5k, with 4ghz i7, 295x GPU, 3.1TB fusion drive. Bought the machine so I could dual boot - I need windows for VR Dev work.
I've spent the last week and a half on tech support calls with Apple Senior Tech agents, and Microsoft agents as well, and today have been told that indeed this machine cannot run windows 8.1. Apparently Apple engineering knows about the issue, but says the problem is microsoft's. Ugh.
The latest iteration of the issue comes when installing 8.1 onto an external thunderbolt SSD (without even using boot camp) - I go through the EFI installer, convert the drive to GPT, format it as ntfs, but when I select the partition to install onto, the installer says it can't find the partition it just created. Smuh?
I've also tried the install through boot camp. This installation actually worked twice, but the install was unstable. After booting back into osX, then returning to Windows, the windows install went corrupt and couldn't be repaired. Subsequent attempts to install windows yielded a flurry of different errors, including "windows doesn't support GPT in this mode" or "the disk is locked, please unlock the disk" or "MBR must be converted to GPT" (where once I converted to GPT, the drive could no longer be found, despite the operation completing successfully.)
At any rate, it's a huge mess. I'd happily return the machine for a different config, but the company I bought it from will only swap it for a similar model -- so I've spent a pile on a machine that does not function as advertised; apple says "too bad, talk to Microsoft." Microsoft says "too bad, we've never seen this, this is an apple issue."
Has anyone out there gotten windows up and running on an iMac5k with fusion drive? If so, did you have to go through a crazy maze to make it work?
Any help is appreciated.
Thanks,
MC

Michael Conelly wrote:
After much gnashing of teeth, and a half dozen support calls, I'd all but given up. I finally seem to have solved this though - sort of - by installing windows 8.1 on boot camp on an older iMac, then cloning the bootcamp disk to an external thunderbolt drive via Winclone. That worked seamlessly, sticking to winclone's instructions, and I can boot via EFI to Windows 8.1 on the new iMac. So far so good.
I usually install W8.1 via EFI by using DU and a Free Space partition. The 3TB Fusion is first split into the underlying SSD/HDD physicals. OSX and Windows OSes are installed on SSD via EFI (no BCA). The OSX part and half the HDD are then used to create a new CS volume. The other HDD half becomes NTFS for non-Windows OS files. The Hybrid MBR method is completely unsatisfactory with the 3TB Fusion drive.
How is the TB/Winclone image for performance of the OS (since pagefile.sys is also on the TB)?

Unable to capture DV to FCE, apple support told me a PC is the way forward!

Hi there
I recently bought an apple imac with a view to editing DV footage taken previously.
I had captured some of these tapes on to a PC before buying an imac. These files I was able to edit on FCE and imovie (once I had transferred them from the pc hard drive). HOWEVER although I could control my DV camera through imovie and FCE none of my old DV tapes could be captured to the imac. An error message states that the frame rate is incorrect.
I have apple care protection and have spent ages trying to get support for this only to be told by apple support that FCE and imovie will not capture my old DV tapes! The support person told me that I should go back to a PC if I want to do the job properly!
Unfortunately I have just spent thousands on this very nice looking imac (and FCE) that is apparently unable to do the most basic capturing. Does anybody have any ideas (other than going back to pc) for getting my DV footage captured?
Needles to say I have found all this incredibly frustrating as a new apple user. Are these sorts of issues common to imacs?
cheers
rupert

Hey Rich,
thanks for getting back to me,
I shot tape previously (in 2000) on a sony mini DV camcorder set to SP. I have since bought a new sony mini DV camcorder (DCR-HC40 NTSC).
With the new camera and a PC I was able to capture my 2000 tapes and edit them. I was also able to edit the earlier footage I had transffered from my PC hard drive to the i-mac on i-movie and FCE.
Unfortunatley everytime I have tried to capture my old tapes directly onto the i-mac I have had the message "preview disabled" from FCE and the following from i-movie:
"The camera is sending half-sized frames, which iMovie can’t accept. Check your camera’s record mode (this is the setting that affects recording quality, which determines the total recording time on a tape). The mode must be set to “SP” or “LP.” If that doesn't help, try removing all the cables and batteries from the camera, wait a minute, replace them, and then reset the date, time, and record mode."
I have spent weeks on the support site and found a thread that recommended re-installing quicktime etc but nothing has worked.
I connect to the i-mac via firewire and am able to control the camera, capture my newly recorded miniDV's (so it is not a problem with the proprietary software application etc) but nothing seems to work for my old tapes.
Apple support told me that apple doesn't do older miniDV's and that a pc would be the only way I could capture my tapes. I couldn't believe it! Unfortuatley I no longer have access to my old pc.
Any ideas? Is there any other way of getting DV onto my i-mac?
And thanks for your interest in my problem here
regards
rupert

Support package / add on import error in DB2 V9.1 / windows 2003 system

Hi
I have installed ERP 6.0 IDES version in Windows 2003 server with DB2 LUW 9.1 / FP5.
I have selected "Row Compression" and "Deferred Table Creation" during installation.
Now when I am importing add on BI Content 7.03, I am getting error during Movename tabs phase.
Error in phase: IMPORT_PROPER
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package ALL, tp step "6", return code 0008
The error message in the file D:\usr\sap\trans\log\P090113.IDS is as follows,
2 ETP301
3 ETP361 "96" Shadow-Nametabs activated, DDL executed
2 ETP362 "6" Shadow-Nametab activations failed
2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/01/13 02:57:51")
2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/01/13 02:58:07")
2 ETP301
1 ETP172 MOVE OF NAMETABS
1 ETP110 end date and time : "20090113025807"
1 ETP111 exit code : "8"
1 ETP199 ######################################
I have read some notes it may be due to "Row compression" and "Deffered table creation" option in DB2. Please help me in resolving this issue if it is DB2 related.
Regards,
Nallasivam.D

Hi,
Please find the real error message which I found in the same log file. This is a new installation.
System configuration details:
ERP 6.0 IDES SR3 + Windows 2003 enterprise server SP2 + DB2 V9.1 / FP5
BASIS and ABAP support pack level: (700) 13.
Error message:
3 ETP399 INDEX IN "IDS#BTABI"
3 ETP399 LONG IN "IDS#BTABD COMPRESS YES"
3 ETP399
2WETP000 02:53:26: Retcode 1: error in DDL statement for "/OSP/T_REPINFO                " - repeat
2EETP345 02:53:38: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#BTABD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/OSP/T_REPINFO
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:05: Retcode 1: error in DDL statement for "/SAPPO/CMP_ASG                " - repeat
2EETP345 02:54:17: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CMP_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:17: error in DDL, nametab for "/SAPPO/CMP_ASG" not activated
3 ETP399 IN "IDS#POOLD"
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:17: Retcode 1: error in DDL statement for "/SAPPO/CSCRN_HDR              " - repeat
2EETP345 02:54:29: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CSCRN_HDR
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:29: error in DDL, nametab for "/SAPPO/CSCRN_HDR" not activated
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:29: Retcode 1: error in DDL statement for "/SAPPO/F_ASG                  " - repeat
2EETP345 02:54:41: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/F_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:41: error in DDL, nametab for "/SAPPO/F_ASG" not activated
Regards,
Nallasivam.D

Supporting STLport in TTClasses

Similar Messages

Maybe you are looking for