[Firebird-devel] [FB-Tracker] Created: (CORE-3721) changeDBAPassword.sh picks up the ISC_ variables if set.
changeDBAPassword.sh picks up the ISC_ variables if set. Key: CORE-3721 URL: http://tracker.firebirdsql.org/browse/CORE-3721 Project: Firebird Core Issue Type: Bug Components: Installation Affects Versions: 2.5.1 Environment: Linux, perhaps all environments that attempt to change the SYSDBA password at installation time. Reporter: Paul Reeves Priority: Minor If ISC_USER/ISC_PASSWORD are set the changeDBAPassword.sh script fails when it tries to add the new sysdba password because gsec will attempt to use the ISC_ variables. But the user/pw pair does not yet exist in the security database. (Although I didn't try with the variables set to SYSDBA/masterkey. That might work. ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-4298) fbsvcmgr doesn't recognise sts_record_versions and other sts switches
fbsvcmgr doesn't recognise sts_record_versions and other sts switches - Key: CORE-4298 URL: http://tracker.firebirdsql.org/browse/CORE-4298 Project: Firebird Core Issue Type: Bug Components: SVCMGR Affects Versions: 2.5.2 Update 1 Environment: Windows, Linux Reporter: Paul Reeves Priority: Minor This : fbsvcmgr service_mgr user sysdba password masterkey action_db_stats dbname employee sts_record_versions fails with : Unknown switch "sts_record_versions" However this works : fbsvcmgr service_mgr user sysdba password masterkey action_db_stats dbname employee sts_data_pages so in principal if stripping isc_spb_sts_data_pages to sts_data_pages is valid then stripping isc_spb_sts_record_versions to sts_record_versions should also be valid. It also seems as if sts_table and sts_nocreation are unknown switches. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-5284) Firebird fails to build with USE_VALGRIND
Firebird fails to build with USE_VALGRIND - Key: CORE-5284 URL: http://tracker.firebirdsql.org/browse/CORE-5284 Project: Firebird Core Issue Type: Bug Components: Build Issues / Porting Affects Versions: 3.0.0, 4.0 Initial Environment: Linux Reporter: Paul Reeves Priority: Minor The first build problem arrives with DELAYED_EXTENT_COUNT being used in anonymous namespace, before it has been defined globally. That was easy enough to work around. But then this error is thrown: alloc.cpp:1866:51: error: 'class Firebird::MemBlock' has no member named 'length' VALGRIND_MAKE_WRITABLE(object, block->length)); Looking at MemBlock there is certainly no length member, but MemBaseHunk does have one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-5314) UDFs declared with large varchars take excessive time to execute
UDFs declared with large varchars take excessive time to execute Key: CORE-5314 URL: http://tracker.firebirdsql.org/browse/CORE-5314 Project: Firebird Core Issue Type: Bug Components: UDF Affects Versions: 2.5.6 Environment: Windows Reporter: Paul Reeves UDFs declared with large varchars take excessive time to execute An IBPhoenix client reported the following problem to us. A single udf, when declared with a 32k string length takes 20 times longer to execute than the same udf declared with a 16k string length. Likewise, declaring the UDF with a string length of 1K takes half the time again. Here is a quick summary of the times: f_strpos_huge - 60s f_strpos_middling - 3s f_strpos_1024 - 1.5s In all cases the same actual function was executed. The only difference was in the declaration. I have a test case which demonstrates the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-5629) gstat output does not include datetime of analysis
gstat output does not include datetime of analysis -- Key: CORE-5629 URL: http://tracker.firebirdsql.org/browse/CORE-5629 Project: Firebird Core Issue Type: Improvement Components: GSTAT Reporter: Paul Reeves Priority: Minor It would be nice to have a timestamp in a gstat report otherwise it is necessary to rely on the file creation date, which is not always correct. This could be the first line of gstat output, just before the Database "/path/to/my.fdb" line. Perhaps something like Gstat execution timeSep 30, 2017 12:00:00 I would guess that this might be easy enough to add to 2.5.8, 30.3 and 4.0 It might also be useful to add a timestamp at the end of the output as large databases can take quite a while to analyse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Reopened: (CORE-3900) VC runtime installer can reboot system prior to installation finishing
[ http://tracker.firebirdsql.org/browse/CORE-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Reeves reopened CORE-3900: --- I'll take another look. > VC runtime installer can reboot system prior to installation finishing > -- > > Key: CORE-3900 > URL: http://tracker.firebirdsql.org/browse/CORE-3900 > Project: Firebird Core > Issue Type: Bug > Components: Installation > Environment: Windows 7 fresh installation during first boot process >Reporter: Brenden Walker >Assignee: Paul Reeves >Priority: Minor > > If the VC runtime installer needs to reboot to finish installation it will > cause the FB installer to reboot the system with no warning (due to /qn > passed to msiexec) before the FB installer finishes. This page > http://desktopengineer.com/windowsinstallererrorcodes notes that msiexec > returns exit code 3010 if a reboot is needed perhaps running always with > /norestart and setting internal reboot required flag would be preferable. > The only time we've seen this is with freshly imaged Win 7 machines during > the first boot process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
